Re: [Openstack-operators] [openstack-dev] [openstack-community] Forum Schedule - Seeking Community Review
Looks Great, Thanks! -Julia PS - Indeed :( On Tue, Oct 16, 2018 at 4:05 PM Jimmy McArthur wrote: > OK - I think I got this fixed. I had to move a couple of things around. > Julia, please let me know if this all works for you: > > > https://www.openstack.org/summit/berlin-2018/summit-schedule/global-search?t=Kreger > > PS - You're going to have a long week :| > > Julia Kreger > October 16, 2018 at 4:44 PM > Greetings Jimmy, > > Looks like it is still showing up on the schedule that way. I just > reloaded the website page and it still has both sessions scheduled for 4:20 > PM local. Sadly, I don't have cloning technology. Perhaps someone can help > me with that for next year? :) > > -Julia > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > Jimmy McArthur > October 16, 2018 at 12:15 PM > I think you might have caught me while I was moving sessions around. This > shouldn't be an issue now. > > Thanks for checking!! > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > Tim Bell > October 16, 2018 at 1:37 AM > Jimmy, > > While it's not a clash within the forum, there are two sessions for Ironic > scheduled at the same time on Tuesday at 14h20, each of which has Julia as > a speaker. > > Tim > > -Original Message- > From: Jimmy McArthur > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > > Date: Monday, 15 October 2018 at 22:04 > To: "OpenStack Development Mailing List (not for usage questions)" > , > "OpenStack-operators@lists.openstack.org" > > > , "commun...@lists.openstack.org" > > > Subject: [openstack-dev] Forum Schedule - Seeking Community Review > > Hi - > > The Forum schedule is now up > (https://www.openstack.org/summit/berlin-2018/summit-schedule/#track=262). > > If you see a glaring content conflict within the Forum itself, please > let me know. > > You can also view the Full Schedule in the attached PDF if that makes > life easier... > > NOTE: BoFs and WGs are still not all up on the schedule. No need to let > us know :) > > Cheers, > Jimmy > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > Jimmy McArthur > October 15, 2018 at 3:01 PM > Hi - > > The Forum schedule is now up ( > https://www.openstack.org/summit/berlin-2018/summit-schedule/#track=262). > If you see a glaring content conflict within the Forum itself, please let > me know. > > You can also view the Full Schedule in the attached PDF if that makes life > easier... > > NOTE: BoFs and WGs are still not all up on the schedule. No need to let > us know :) > > Cheers, > Jimmy > ___ > Staff mailing list > st...@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/staff > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [openstack-dev] [openstack-community] Forum Schedule - Seeking Community Review
Greetings Jimmy, Looks like it is still showing up on the schedule that way. I just reloaded the website page and it still has both sessions scheduled for 4:20 PM local. Sadly, I don't have cloning technology. Perhaps someone can help me with that for next year? :) -Julia On Tue, Oct 16, 2018 at 11:15 AM Jimmy McArthur wrote: > I think you might have caught me while I was moving sessions around. This > shouldn't be an issue now. > > Thanks for checking!! > > Tim Bell > October 16, 2018 at 1:37 AM > Jimmy, > > While it's not a clash within the forum, there are two sessions for Ironic > scheduled at the same time on Tuesday at 14h20, each of which has Julia as > a speaker. > > Tim > > -Original Message- > From: Jimmy McArthur > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > > Date: Monday, 15 October 2018 at 22:04 > To: "OpenStack Development Mailing List (not for usage questions)" > , > "OpenStack-operators@lists.openstack.org" > > > , "commun...@lists.openstack.org" > > > Subject: [openstack-dev] Forum Schedule - Seeking Community Review > > Hi - > > The Forum schedule is now up > (https://www.openstack.org/summit/berlin-2018/summit-schedule/#track=262). > > If you see a glaring content conflict within the Forum itself, please > let me know. > > You can also view the Full Schedule in the attached PDF if that makes > life easier... > > NOTE: BoFs and WGs are still not all up on the schedule. No need to let > us know :) > > Cheers, > Jimmy > > > ___ > Community mailing list > commun...@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/community > Jimmy McArthur > October 15, 2018 at 3:01 PM > Hi - > > The Forum schedule is now up ( > https://www.openstack.org/summit/berlin-2018/summit-schedule/#track=262). > If you see a glaring content conflict within the Forum itself, please let > me know. > > You can also view the Full Schedule in the attached PDF if that makes life > easier... > > NOTE: BoFs and WGs are still not all up on the schedule. No need to let > us know :) > > Cheers, > Jimmy > ___ > Staff mailing list > st...@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/staff > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [ironic][tripleo][edge] Discussing ironic federation and distributed deployments
Greetings everyone, It looks like the most agreeable time on the doodle[1] seems to be Tuesday September 4th at 13:00 UTC. Are there any objections to using this time? If not, I'll go ahead and create an etherpad, and setup a bluejeans call for that time to enable high bandwidth discussion. -Julia [1]: https://doodle.com/poll/y355wt97heffvp3m On Mon, Aug 27, 2018 at 9:53 AM Julia Kreger wrote: > > Greetings everyone! > > We in Ironic land would like to go into the PTG with some additional > thoughts, requirements, and ideas as it relates to distributed and > geographically distributed deployments. > [trim] ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [ironic][tripleo][edge] Discussing ironic federation and distributed deployments
Greetings everyone! We in Ironic land would like to go into the PTG with some additional thoughts, requirements, and ideas as it relates to distributed and geographically distributed deployments. As you may or may not know, we did take a first step towards supporting some of the architectures needed with conductor_groups this past cycle, but we have two very distinct needs that have been expressed with-in the community. 1) Need to federate and share baremetal resources between ironic deployments. A specification[1] was proposed to try and begin to capture what this would look like ironic wise. At a high level, this would look like an ironic node that actually consumes and remotely manages a node via another ironic deployment. Largely this would be a stand-alone user/admin user deployment cases, where hardware inventory insight is needed. 2) Need to securely manage remote sites with different security postures, while not exposing control-plane components as an attack surface. Some early discussion into this would involve changing Conductor/IPA communication flow[2], or at least supporting a different model, and some sort of light weight intermediate middle-man service that helps facilitate the local site management. With that in mind, we would like to schedule a call for sometime next week where we can kind of talk through and discuss these thoughts and needs in real time in advance of the PTG so we can be even better prepared. We are attempting to identify a time with a doodle[3]. Please select a time and date, so we can schedule something for next week. Thanks, -Julia [1]: https://review.openstack.org/#/c/560152/ [2]: https://review.openstack.org/212206 [3]: https://doodle.com/poll/y355wt97heffvp3m ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Ironic post-deploy cleanup change backport
Greetings everyone, We in the Ironic community have recently been discussing back porting a bug fix[1] to stable/queens which addresses cases where where a baremetal node is prevented from being able to be deployed due to an orphaned VIF (neutron port) record in ironic. Under normal circumstances, Nova removes the records from Ironic when removing an instance. We found that in some cases, this might not always succeed due to extended locking of a bare metal node undergoing cleaning. Typically we've seen this where IPMI BMCs do not immediately replying to power actions. Our fix adds the logic to ironic itself to go ahead and clean-up neutron port attachment records when we are un-deploying a baremetal node. For users of Ironic through nova, there is no difference. For users of ironic where they are directly interacting with ironic's API, and where the environment also utilizes Neutron, there is a slight behavior difference in that the `openstack baremetal node vif detach` will not be needed after un-deploying a baremetal node. This also means that the attachment will need to be re-added if the node is being deployed manually. Please let us know if there are any questions or concerns. We have not yet merged this back-port patch, but feel that the benefit to it greatly out-weighs the negative impact. -Julia [1]: https://review.openstack.org/#/c/562314/ ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
