Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

On Thu, Oct 19, 2017 at 11:23 PM, Gabriele Cerami wrote: > On 19 Oct, Sam Yaple wrote: > > So it seems tripleo is building *all* images and then pushing them. > > Reworking your number leads me to believe you will be consuming 10-15GB > in > > total on Dockerhub. Kolla images

[openstack-dev] [infra] Short gerrit / zuul outage 2017-10-20 20:00UTC

Hello, We plan a short outage (<30 minutes) of gerrit and zuul on 2017-10-20 20:00UTC to facilitate project rename requests. In flight jobs should be restarted, but if something does go missing a "recheck" comment will work. Thanks, -i

Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

On 19 Oct, Sam Yaple wrote: > So it seems tripleo is building *all* images and then pushing them. > Reworking your number leads me to believe you will be consuming 10-15GB in > total on Dockerhub. Kolla images are only the size that you posted when > built as seperate services. Just keep building

[openstack-dev] Fwd: [Openstack-operators][tc] [keystone][all] v2.0 API removal

Should this kind of change be discussed and have an agreement of the TC and User committee? -- Forwarded message -- From: Lance Bragstad Date: Fri, Oct 20, 2017 at 12:08 AM Subject: [Openstack-operators] [keystone][all] v2.0 API removal To: "OpenStack

Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

On Thu, Oct 19, 2017 at 9:38 PM, Gabriele Cerami wrote: > On 19 Oct, Sam Yaple wrote: > > docker_image wouldn't be the best place for that. Buf if you are looking > > for a quicker solution, kolla_docker was written specifically to be > license > > compatible for openstack.

Re: [openstack-dev] [keystone][all] v2.0 API removal

Keystone is one project that all other OpenStack projects use, so personally I think the change to remove the API which are widely used should be discussed at TC meeting . As far as I know ,not all OpenStack projects support the keystone v3 domain (domain, project,user) as well as keystone, you

[openstack-dev] [nova] Sort order when filtering by changes-since

Nova has two specs approved for Queens for filtering instance actions and migrations by the 'changes-since' filter, which filters on the updated_at field. https://review.openstack.org/#/c/507762/ https://review.openstack.org/#/c/506030/ Those APIs don't take a sort key like the servers API

Re: [openstack-dev] [release] Release countdown for week R-18, October 21-27

Thanks for the election shout out Sean :) -Kendall (diablo_rojo) On Thu, Oct 19, 2017, 11:45 PM Sean McGinnis wrote: > At last, our regular release countdown email. > > Development Focus > - > > We are now past the Queens-1 milestone. While there are

Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

On 19 Oct, Sam Yaple wrote: > docker_image wouldn't be the best place for that. Buf if you are looking > for a quicker solution, kolla_docker was written specifically to be license > compatible for openstack. its structure should make it easily adapted to > delete an image. And you can copy it and

[openstack-dev] [release] Release countdown for week R-18, October 21-27

At last, our regular release countdown email. Development Focus - We are now past the Queens-1 milestone. While there are still some Zuul job issues being worked through, all cycle-following projects should have posted a release request for the first milestone. If you have not

Re: [openstack-dev] OpenStack Dev Digest is Open to Volunteers!

On 19:06 Oct 17, Mike Perez wrote: > Hey all, > > The OpenStack Dev Digest has been receiving great feedback from various > members > of our community as being a good resource to get important summaries of > threads > they might be interested in responding back to and/or being informed on. > >

[openstack-dev] [TripleO] Deployment workflow changes for ui/client

I've been looking at how we can hook up the deployment changes for config-download[1] with the existing deployment workflows in Mistral. However, it seems we have not sufficiently abstracted the logic to do a "deployment" behind a given workflow(s). The existing things a client (or UI) has to do

Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

Cool thanks, I'll have to watch for this and see how it goes. I thought there was some specific things that changed every time a dockerfile was rendered (which would make it different each run) but I may have been seeing things (or it's been fixed). Michał Jastrzębski wrote: On 19 October

Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

On 19 October 2017 at 13:37, Michał Jastrzębski wrote: > On 19 October 2017 at 13:32, Joshua Harlow wrote: >> This reminded me of something I wanted to ask. >> >> Is it true to state that only way to get 'fully' shared-base layers is to >> have

Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

On 19 October 2017 at 13:32, Joshua Harlow wrote: > This reminded me of something I wanted to ask. > > Is it true to state that only way to get 'fully' shared-base layers is to > have `kolla-build` build all the projects (that a person/company/other may > use) in one

Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

This reminded me of something I wanted to ask. Is it true to state that only way to get 'fully' shared-base layers is to have `kolla-build` build all the projects (that a person/company/other may use) in one invocation? (in part because of the jinja2 template generation which would cause

[openstack-dev] [tripleo] CI Status & Where to find your patch's status in CI

Hey Folks, So the gate queue is quite backed up due to various reasons. If your patch has been approved but you're uncertain of the CI status please, please, please check the dashboard[0] before doing anything. Do not rebase or recheck things currently in a queue somewhere. When you rebase a

Re: [openstack-dev] [Release-job-failures][release][neutron][powervm] Pre-release of openstack/networking-powervm failed

We are still working on fixing up the release jobs to work after the zuulv3 migration. Please do not tag releases until we announce that it is OK. Excerpts from zuul's message of 2017-10-19 20:04:07 +: > Build failed. > > - trigger-readthedocs >

Re: [openstack-dev] [keystone][all] v2.0 API removal

On Thu, Oct 19, 2017 at 11:49 AM, Lance Bragstad wrote: > Yeah - we specifically talked about this in a recent meeting [0]. We > will be more verbose about this in the future. > I'm glad to see a review of this. In reading the meeting logs, I understand it was well

Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

docker_image wouldn't be the best place for that. Buf if you are looking for a quicker solution, kolla_docker was written specifically to be license compatible for openstack. its structure should make it easily adapted to delete an image. And you can copy it and cut it up thanks to the license.

Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

For kolla, we were thinking about a couple of optimization that should greatly reduce the space. 1. only upload to the hub based on stable versions. The updates are much less frequent. 2. fingerprint the containers. base it on rpm/deb list, pip list, git checksums. If the fingerprint is the

[openstack-dev] [Congress] proposed change to IRC meeting time

Hi all, Here is a proposal (no actual change until further notice) to move the weekly Congress team meeting from Thursdays 00:00 UTC to Fridays 02:30 UTC in order to make the meeting time more bearable for India while still being workable for East Asia and the Americas. The time remains very bad

Re: [openstack-dev] [keystone][all] v2.0 API removal

Yeah - we specifically talked about this in a recent meeting [0]. We will be more verbose about this in the future. [0] http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-10-10-18.00.log.html#l-107 On 10/19/2017 12:00 PM, Alex Schultz wrote: > On Thu, Oct 19, 2017 at 10:08 AM,

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, If you were hoping for startling news, well, you're going to be disappointed. We did, however, have a perfectly enjoyable meeting today. A question had been raised about creating a guideline for 'changes-since' filtering in an API [5], and we debated whether it

Re: [openstack-dev] [keystone][all] v2.0 API removal

On Thu, Oct 19, 2017 at 10:08 AM, Lance Bragstad wrote: > Hey all, > > Now that we're finishing up the last few bits of v2.0 removal, I'd like to > send out a reminder that Queens will not include the v2.0 keystone APIs > except the ec2-api. Authentication and validation of

[openstack-dev] [keystone][all] v2.0 API removal

Hey all, Now that we're finishing up the last few bits of v2.0 removal, I'd like to send out a reminder that *Queens* will not include the *v2.0 keystone APIs* except the ec2-api. Authentication and validation of v2.0 tokens has been removed (in addition to the public and admin APIs) after a

Re: [openstack-dev] [nova][ironic] Concerns over rigid resource class-only ironic scheduling

On 19 October 2017 at 15:38, Jay Pipes wrote: > On 10/16/2017 05:31 AM, Nisha Agarwal wrote: > >> Hi Matt, >> >> As i understand John's spec https://review.openstack.org/#/c/507052/ < >> https://review.openstack.org/#/c/507052/>, it is actually a replacement >> for

[openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

Hi, our CI scripts are now automatically building, testing and pushing approved openstack/RDO services images to public repositories in dockerhub using ansible docker_image module. Promotions have had some hiccups, but we're starting to regularly upload new images every 4 hours. When we'll get

Re: [openstack-dev] [nova][ironic] Concerns over rigid resource class-only ironic scheduling

On 10/16/2017 05:31 AM, Nisha Agarwal wrote: Hi Matt, As i understand John's spec https://review.openstack.org/#/c/507052/ , it is actually a replacement for capabilities(qualitative only) for ironic. It doesnt cover the quantitative capabilities as

[openstack-dev] [Neutron][L3-subteam] Weekly IRC meeting cancelled on October 19th

Dear L3 sub-team Neutrinos, Due to unexpected agenda conflicts of several of the team members, we will cancel today's meeting. We will resume normally on the 26th Regards Miguel __ OpenStack Development Mailing List (not

Re: [openstack-dev] [all][tc] TC Candidates: what does an OpenStack user look like?

"Right, so we all agree that what we *don't* want is TC candidates saying "I'm here to represent the interests of user community X against those of evil user community Y", all of the X users voting for X candidates and not Y candidates, and then the elected X members voting to block anything that

[openstack-dev] [keystoneauth] [osc] [ironic] Usage of none loader in the CLI

Hi! I'd like to discuss the usage of the new noauth plugin to keystoneauth, which was introduced in [1]. The docstring of the loader says it is intended to be used during adapter initialization along with endpoint_override. But what about the CLI usage in the OpenStack client? I was trying to

[openstack-dev] [nova][neutron] Use neutron's new port binding API

Hi matt You not only currently so I taught I would respond to your question regarding the workflow via email. http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2017-10-18.log.html#t2017-10-18T20:29:02 mriedem 1. conductor asks scheduler for a host20:29

Re: [openstack-dev] [ptls] Sydney Forum Project Onboarding Rooms

Added Ansible to my list with the three of you as speakers :) -Kendall (diablo_rojo) On Tue, Oct 17, 2017 at 7:28 AM Jean-Philippe Evrard < jean-phili...@evrard.me> wrote: > Hello, > > I'd be happy to have a room for OpenStack-Ansible. > > I'll be there, and probably more ppl, like Kevin

Re: [openstack-dev] [ptls] Sydney Forum Project Onboarding Rooms

Added Neutron to my list. -Kendall (diablo_rojo) On Tue, Oct 17, 2017 at 7:28 AM Miguel Lavalle wrote: > Neutron - Miguel Lavalle - mig...@mlavalle.com > > On Mon, Oct 16, 2017 at 9:39 PM, Jeffrey Zhang > wrote: > >> I am the speaker. Michal

Re: [openstack-dev] [oslo][mistral] Mistral expressions package

Ok, thanks for your input. I’d personally say it’s not really worth it but if Bob wants to do it that’s ok. Thanks Renat Akhmerov @Nokia On 19 Oct 2017, 12:46 +0700, ChangBo Guo , wrote: > The dependencies of  mistral expressions package make it hard to be adopted > as a