I know tacker project is using heat-translator and tosca-parser projects. Who
can tell
if other projects in OpenStack tents are using them?
regards,
yong sheng gong
At 2018-06-23 01:25:39, "Zane Bitter" wrote:
>On 21/06/18 16:37, Sean McGinnis wrote:
>>>
>>> Apparently heat-translator has a
Hi Muhammad,
I am not sure what is the exact problem, but here is the list of things you
might want to check:
1. Make sure the security group is open. This document explains how to find
the security group(s) of the container:
Great, thanks to the API SIG!
On 23/06/18 06:53, Flint WALRUS wrote:
Oh! That’s its truly a sweet sweet attention, that will indeed really
help us to focus on what we have to do without having to goes through
an extensive email back and forth :-)
Thanks a lot!!
Le ven. 22 juin 2018 à 22:48,
Oh! That’s its truly a sweet sweet attention, that will indeed really help
us to focus on what we have to do without having to goes through an
extensive email back and forth :-)
Thanks a lot!!
Le ven. 22 juin 2018 à 22:48, Ed Leafe a écrit :
> On Jun 15, 2018, at 5:42 PM, Gilles Dubreuil
On Jun 15, 2018, at 5:42 PM, Gilles Dubreuil wrote:
>
> This initial patch [1] allows to retrieve networks, subnets.
>
> This is very easy, thanks to the graphene-sqlalchemy helper.
>
> The edges, nodes layer might be confusing at first meanwhile they make the
> Schema Relay-compliant in
> > > Apparently heat-translator has a healthy ecosystem of contributors and
> > > users, but not of maintainers, and it remaining a deliverable of the Heat
> > > project is doing nothing to alleviate the latter problem. I'd like to find
> > > it a home that _would_ help.
> > >
> >
> > I'd be
On 21/06/18 16:37, Sean McGinnis wrote:
Apparently heat-translator has a healthy ecosystem of contributors and
users, but not of maintainers, and it remaining a deliverable of the Heat
project is doing nothing to alleviate the latter problem. I'd like to find
it a home that _would_ help.
I'd
HTML: https://anticdent.org/placement-update-18-25.html
This is placement update 18-25, a weekly update of ongoing
development related to the [OpenStack](https://www.openstack.org/)
[placement
service](https://developer.openstack.org/api-ref/placement/).
This is a "contract" version, meaning
s/review the new version is/review the new version/
Regards,
Sundar
On 6/22/2018 8:06 AM, Nadathur, Sundar wrote:
Hello folks,
The os-acc spec [1] has been updated substantially. Please review the
new version is https://review.openstack.org/#/c/577438/ .
The background for the update is that
Hello folks,
The os-acc spec [1] has been updated substantially. Please review the
new version is https://review.openstack.org/#/c/577438/ .
The background for the update is that several important aspects were
raised as comments on the previous spec ([1], [2]). An alternative
workflow for
Sounds great. Going to get a cold beer to celebrate that ;)
Witek
> -Original Message-
> From: Julien Danjou
> Sent: Freitag, 22. Juni 2018 16:51
> To: Bedyk, Witold
> Cc: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev]
On Fri, Jun 22 2018, Bedyk, Witold wrote:
> You've said lacking manpower is currently the main issue in Ceilometer which
> stops you from accepting new publishers and that you don't want to add
> maintenance overhead.
>
> We're offering help on maintaining the project.
Oh cool, I misunderstood.
Also:
keystoneauth1 3.9.0 was released. Its new feature is the ability to set
raise_exc on the Adapter object so you don't have to do it per request.
Here's a patch that makes use of the feature:
https://review.openstack.org/#/c/577437/
-efried
On 06/22/2018 06:53 AM, Colleen Murphy wrote:
> #
On Fri, 22 Jun 2018, Bedyk, Witold wrote:
You've said lacking manpower is currently the main issue in
Ceilometer which stops you from accepting new publishers and that
you don't want to add maintenance overhead.
I've lost track of the details of the thread, can you remind me why
keeping the
You've said lacking manpower is currently the main issue in Ceilometer which
stops you from accepting new publishers and that you don't want to add
maintenance overhead.
We're offering help on maintaining the project.
Cheers
Witek
> -Original Message-
> From: Julien Danjou
> Sent:
On Fri, Jun 22 2018, Bedyk, Witold wrote:
> I know it's not how it normally works, but in that case it seems to be a clear
> win-win situation.
I'm sorry, I really don't see what's the win for Ceilometer or its
developer. Could you elaborate?
--
Julien Danjou
;; Free Software hacker
;;
Hi all,
I thought it might be useful to start an irregular update on Kayobe,
covering recent and upcoming events. This follows on from the update blog
article [1] that I wrote a couple of months ago (which includes a video and
asciinema demo!).
# OpenStack-related
The switch to using OpenStack
Hi Julien and Mehdi,
I obviously care more about Monasca and integration with other OpenStack
projects. If the publisher wouldn't be an important piece of the puzzle I
wouldn't be pushing this.
I have stressed a couple of times that we are ready to take the complete
responsibility for the
# Keystone Team Update - Week of 18 June 2018
## News
### Default Roles Fallout
Our change to automatically create the 'reader' and 'member' roles during
bootstrap[1] caused some problems in the CI of other projects[2]. One problem
was that projects were manually creating a 'Member' role, and
Hi Hongbin,
Many thanks, got it running, that was awesom... :) The problem was
unsynched time. I installed chrony and it started working.
Now I am running into another problem; the networking of the container. The
container gets started, I can shell into it through appcontainer API, it
even gets
On June 22, 2018 8:01 am, Flint WALRUS wrote:
About your code, I feel that we should extract the schemas from the base.py
under neutron/api/graphql/schemas/ right now before the code became to
large, that would then allows for a better granularity.
Thanks.
Since this is the graphql branch,
On Friday, 22 June 2018 05:00:16 CEST Joe Topjian wrote:
> Hello,
>
> I originally posted this to the general openstack list to get a sanity
> check on what I was seeing. Jeremy F reached out and confirmed that, so I'm
> going to re-post the details here to begin a discussion.
Hi,
thanks for
Hi Gilles, I just had a look at your patch, cool, thanks for the work.
ok, that good to start with a limited subsets of query types indeed, you're
right.
Ok, perfect for the patch to branch, I don't know why but I had the feeling
that you were requesting for the branch to be merged back and not
On 22/06/18 15:57, Flint WALRUS wrote:
Hi everyone,
Thanks for the updates and support, that appreciated.
@Gilles, did you already implemented all the service types?
We have query types for networks and subnets for now.
Before we add more we are going to focus on oslo policies so we can
24 matches
Mail list logo
