Re: [Openstack-operators] [openstack-dev] [forum] Sydney Forum etherpad list

[Michael Still]

The privsep session doesn't appear to be in that list. Did it get dropped
or something?

Michael

On Wed, Nov 1, 2017 at 12:04 AM, Thierry Carrez 
wrote:

> Hi everyone,
>
> Etherpads for the Forum sessions in Sydney can be found here:
>
> https://wiki.openstack.org/wiki/Forum/Sydney2017
>
> If you are moderating such a session and the etherpad is missing, please
> add it !
>
> --
> Thierry Carrez (ttx)
>
> __
> 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] [Forum] Moderators needed!

[Alan Meadows]

Apologizes for resurrecting a dead thread but context is important. We had
a great discussion in Boston on this topic especially around health APIs
and everyone was really very understanding of the over-size brain
situation.  We didn't do our best bringing back the output of that to the
mailing list, but we have a chance to try again in Sydney with Part II!

This time we'll make sure the discussion works its way back properly to the
development mailing list.

https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20472/cloud-native-designrefactoring-across-openstack-part-ii

I'd encourage everyone who has an interest in this topic to attend.  See
you in Sydney.

Alan Meadows

On Fri, Apr 28, 2017 at 6:07 AM, Jay Pipes  wrote:

> On 04/28/2017 08:22 AM, Shamail Tahir wrote:
>
>> Hi everyone,
>>
>> Most of the proposed/accepted Forum sessions currently have moderators
>> but there are six sessions that do not have a confirmed moderator yet.
>> Please look at the list below and let us know if you would be willing to
>> help moderate any of these sessions.
>>
>
> 
>
> Cloud-Native Design/Refactoring across OpenStack
>> > e/events/18767/cloud-native-designrefactoring-across-openstack>
>>
>
> Hi Shamail,
>
> The one above looks like Alan (cc'd) is the moderator. :)
>
> Despite him having a awkwardly over-sized brain -- which unfortunately
> will limit the number of other people that can fit in the room -- I do
> think Alan will be a good moderator.
>
> Best,
> -jay
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Live migration failures

[Mike Lowe]

I did not, it appears to be related to changing libvirt versions.  It’s no 
longer as tolerant of being sloppy with device addresses.  The last change for 
this section of code was a year ago if I read the git blame correctly.

> On Nov 2, 2017, at 2:11 PM, Chris Friesen  wrote:
> 
> On 11/02/2017 08:48 AM, Mike Lowe wrote:
>> After moving from CentOS 7.3 to 7.4, I’ve had trouble getting live migration 
>> to work when a volume is attached.  As it turns out when a live migration 
>> takes place the libvirt driver rewrites portions of the xml definition for 
>> the destination hypervisor and gets it wrong.  Here is an example.
> 
> Did you change versions of OpenStack as well?
> 
> Chris
> 
> 
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Openstack release compatibility

[Chris Friesen]

On 10/31/2017 01:13 AM, haad wrote:

Hi,

We have an OSA installation with 10-12 compute nodes running Mitaka on Ubuntu
16.04. As initially we have not prepared any long term update strategy we would
like to create one now. Plan would be to upgrade it to new OSA
release(Ocata/Pike/Queens) in near future.

Our original plan was to update management/networking/backend at once by using
rolling updates to newer release and then upgrade compute nodes one by one to
new release.. I think that [2] provides a general upgrade manual. Is there any
document describing how are different OSA releases compatible ? Is there any
policy in place about backward compatibility ?


As a general rule, OpenStack only supports an online upgrade of one version at a 
time.  That is, controller nodes running version N can talk to compute nodes 
running version N-1.


If you can tolerate downtime of the API layer, there has been some discussion 
around "skip-level" upgrades.


Chris


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Live migration failures

[Chris Friesen]

On 11/02/2017 08:48 AM, Mike Lowe wrote:

After moving from CentOS 7.3 to 7.4, I’ve had trouble getting live migration to 
work when a volume is attached.  As it turns out when a live migration takes 
place the libvirt driver rewrites portions of the xml definition for the 
destination hypervisor and gets it wrong.  Here is an example.


Did you change versions of OpenStack as well?

Chris


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Clear Linux guest issues (maybe UEFI boot issues?)

[Jonathan Proulx]

Hi All,

This is low priority poking but I have a sort of puzzling situation.

Wanted to play with Clear linux (which is uefi only) to see what it
was about  so grabbed some images and obviously tried to throw them on
my OpenStack cloud.

After learning how to enable EUFI booting (hw_firmware_type='uefi' in
image metadata and ovfm package on hypervisors) it still just hangs
trying to boot, no serial out, uninialized VNC console, no ping.

Running manually under KVM on my workstation (same Ubuntu 16.04 as
hypervisors) I can get it to go.

Nova generated qemu command: https://pastebin.com/VarvB6Cs
Simpler manual command (works): https://pastebin.com/BfJpXYRm

any clues?

thanks,
-Jon
-- 

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Live migration failures

[Mike Lowe]

Look at comment #2, it’s me.

> On Nov 2, 2017, at 11:34 AM, Sergio Cuellar Valdes 
>  wrote:
> 
> Hi Mike,
> 
> Which version of OpenStack are you using ? Do the normal migrations work ? 
> 
> I found a bug that looks like your problem [1]
> 
> [1] https://bugs.launchpad.net/nova/+bug/1715569 
> 
> 
> Cheers,
> Sergio
> 
> On 2 November 2017 at 08:48, Mike Lowe  > wrote:
> After moving from CentOS 7.3 to 7.4, I’ve had trouble getting live migration 
> to work when a volume is attached.  As it turns out when a live migration 
> takes place the libvirt driver rewrites portions of the xml definition for 
> the destination hypervisor and gets it wrong.  Here is an example.
> 
> It turns this:
> 
> disk device="disk" type="network">
> 
> 
>  uuid="1a790a26-dd49-4825-8d16-3dd627cf05a9"/>
> 
>  name="cinder-volumes/volume-de400476-b68a-45a2-b04f-739313f42bef" 
> protocol="rbd">
> 
> 
> 
> 
> 
> de400476-b68a-45a2-b04f-739313f42bef
> 
> 
> 
> Into this:
> 
> 
> 
> 
>  uuid="1a790a26-dd49-4825-8d16-3dd627cf05a9"/>
> 
>  name="cinder-volumes/volume-de400476-b68a-45a2-b04f-739313f42bef" 
> protocol="rbd">
> 
> 
> 
> 
> 
> de400476-b68a-45a2-b04f-739313f42bef
> 
> 
> 
> Note the address change, libvirt will attempt to put this undefined disk at 
> 0:0:0 which conflicts with the root disk and causes the migration to fail.  
> While this may be a libvirt bug I can’t imagine anything good would come from 
> changing the scsi address of your disks mid flight so steps should be taken 
> in nova if rewriting the definition to preserve the address.
> 
> Here is my question, when exactly would you want to change the definition of 
> an attached volume?
> 
> 
> 
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org 
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators 
> 
> 
> 
> 
> -- 
>  Sergio Cuéllar │DevOps Engineer
>  KIO NETWORKS
>  Mexico City Phone (52) 55 8503 2600 ext. 4335
>  Mobile: 5544844298
>  www.kionetworks.com 
> 
> 
> ***
> “Este mensaje es confidencial.  Si usted no es el destinatario de este 
> mensaje, le suplicamos se lo notifique al remitente mediante un correo 
> electrónico y que borre el presente mensaje y sus anexos de su computadora 
> sin retener una copia de los mismos. No debe copiar este mensaje o usarlo 
> para cualquier propósito ni divulgar su contenido. KIO Networks se reserva el 
> derecho de monitorear todas las comunicaciones de correo electrónico 
> (relacionadas o no con KIO Networks) que se transmitan a través de su 
> sistema. Muchas gracias.
> This email is confidential and may also be privileged.  If you are not the 
> intended recipient please immediately advise the sender by reply e-mail and 
> delete this message and its attachments from your computer without retaining 
> a copy. You should not copy it or use it for any purpose nor disclose its 
> contents to any other person. KIO Networks reserves the right to monitor all 
> email communications (whether related to the business of KIO Networks or not) 
> through its networks. Thank you.”
> 
> ***___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Live migration failures

[Sergio Cuellar Valdes]

Hi Mike,

Which version of OpenStack are you using ? Do the normal migrations work ?

I found a bug that looks like your problem [1]

[1] https://bugs.launchpad.net/nova/+bug/1715569

Cheers,
Sergio

On 2 November 2017 at 08:48, Mike Lowe  wrote:

> After moving from CentOS 7.3 to 7.4, I’ve had trouble getting live
> migration to work when a volume is attached.  As it turns out when a live
> migration takes place the libvirt driver rewrites portions of the xml
> definition for the destination hypervisor and gets it wrong.  Here is an
> example.
>
> It turns this:
>
> disk device="disk" type="network">
> 
> 
> 
> 
>  name="cinder-volumes/volume-de400476-b68a-45a2-b04f-739313f42bef"
> protocol="rbd">
> 
> 
> 
> 
> 
> de400476-b68a-45a2-b04f-739313f42bef
> 
> 
>
> Into this:
>
> 
> 
> 
> 
> 
>  name="cinder-volumes/volume-de400476-b68a-45a2-b04f-739313f42bef"
> protocol="rbd">
> 
> 
> 
> 
> 
> de400476-b68a-45a2-b04f-739313f42bef
> 
> 
>
> Note the address change, libvirt will attempt to put this undefined disk
> at 0:0:0 which conflicts with the root disk and causes the migration to
> fail.  While this may be a libvirt bug I can’t imagine anything good would
> come from changing the scsi address of your disks mid flight so steps
> should be taken in nova if rewriting the definition to preserve the address.
>
> Here is my question, when exactly would you want to change the definition
> of an attached volume?
>
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>



-- 
* Sergio Cuéllar │DevOps Engineer*
 KIO NETWORKS
 Mexico City Phone (52) 55 8503 2600 ext. 4335
 Mobile: 5544844298
 www.kionetworks.com

-- 


*

*“Este mensaje es confidencial.  Si usted no es el destinatario de este 
mensaje, le suplicamos se lo notifique al remitente mediante un correo 
electrónico y que borre el presente mensaje y sus anexos de su computadora 
sin retener una copia de los mismos. No debe copiar este mensaje o usarlo 
para cualquier propósito ni divulgar su contenido. KIO Networks se reserva 
el derecho de monitorear todas las comunicaciones de correo electrónico 
(relacionadas o no con KIO Networks) que se transmitan a través de su 
sistema. **Muchas gracias.*

*This email is confidential and may also be privileged.  If you are not the 
intended recipient please immediately advise the sender by reply e-mail and 
delete this message and its attachments from your computer without 
retaining a copy. You should not copy it or use it for any purpose nor 
disclose its contents to any other person. KIO Networks reserves the right 
to monitor all email communications (whether related to the business of KIO 
Networks or not) through its networks. Thank you.”*
*
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Live migration failures

[Mike Lowe]

After moving from CentOS 7.3 to 7.4, I’ve had trouble getting live migration to 
work when a volume is attached.  As it turns out when a live migration takes 
place the libvirt driver rewrites portions of the xml definition for the 
destination hypervisor and gets it wrong.  Here is an example.

It turns this:

disk device="disk" type="network">










de400476-b68a-45a2-b04f-739313f42bef



Into this:












de400476-b68a-45a2-b04f-739313f42bef



Note the address change, libvirt will attempt to put this undefined disk at 
0:0:0 which conflicts with the root disk and causes the migration to fail.  
While this may be a libvirt bug I can’t imagine anything good would come from 
changing the scsi address of your disks mid flight so steps should be taken in 
nova if rewriting the definition to preserve the address.

Here is my question, when exactly would you want to change the definition of an 
attached volume?



___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [QA] Sydney Summit

[Andrea Frittoli]

Dear all,

A few of us from the QA team will be in Sydney at the OpenStack summit.
We will host and on boarding session on Monday afternoon [0] as well as a
few feedback sessions on QA tools through the week [1][2][3].
A project QA update session will take place on Tuesday [4].

If your interested in OpenStack QA, please join us at one of the sessions,
we welcome all type of contributions - feedback, ideas, code, documentation.

We look forward to meeting you in Sydney!

Andrea Frittoli (andreaf)

[0]
https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20437/qa-project-onboarding

[1]
https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20443/missing-features-and-making-improvements-to-openstack-health

[2]
https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20459/the-state-of-test-runners-and-moving-to-stestr

[3]
https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20505/users-operators-adoption-of-qa-tools-plugins

[4]
https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20385/qa-project-update
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [openstack-ansible] Sydney summit -- We'll be there!

[Jean-Philippe Evrard]

Hello everyone,

A small delegation of our openstack-ansible team will be in Sydney,
and we are looking forward to meeting all of you!

We'll have an ops feedback session during the forum happening on
Monday 6th, 1:30 pm - 2:10 pm.

If you're willing to get started with openstack-ansible, contribute,
or get to know us, please join us on Tuesday 7th,  9:50 - 10:30 AM.

Last, but not least, if you want to know what happened in
openstack-ansible in the last cycle(s) or if you're interested by our
future strategy, that would be on Tuesday 7th, 5:50 pm - 6:10 pm
during our traditional "Project Update" session.

I am looking forward meeting all of you!

Best regards,
Jean-Philippe Evrard (evrardjp)

PS: We have an etherpad listing all these activities and more details
about the ops session here:
https://etherpad.openstack.org/p/osa-sydney-summit-planning

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Openstack release compatibility

[Jean-Philippe Evrard]

On 31 October 2017 at 07:13, haad  wrote:
> Hi,
>
> We have an OSA installation with 10-12 compute nodes running Mitaka on
> Ubuntu 16.04. As initially we have not prepared any long term update
> strategy we would like to create one now. Plan would be to upgrade it to new
> OSA release(Ocata/Pike/Queens) in near future.
>
> Our original plan was to update management/networking/backend at once by
> using rolling updates to newer release and then upgrade compute nodes one by
> one to new release.. I think that [2] provides a general upgrade manual. Is
> there any document describing how are different OSA releases compatible ? Is
> there any policy in place about backward compatibility ?
>
>
>
> [1] https://etherpad.openstack.org/p/osa-newton-xenial-upgrade
> [2] https://wiki.openstack.org/wiki/Upgrade-with-minimal-downtime
>
> --
>
>
> Regards.
>
> Adam
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>

Hello,

I'd advise you to follow the standard OpenStack-Ansible path, which is
upgrading from Mitaka to Newton, then do your ubuntu upgrade to
xenial.
From Newton onwards, we have code taking care of the rolling part of
the upgrade, which should help you getting to Pike, after a series of
upgrades (N->O->P) under ubuntu 16.04.

Best regards,
Jean-Philippe Evrard (evrardjp)

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [openstack-operators][openstack-dev][heat][all] Sydney for all Heat Users, Operators, and Developers

[Rico Lin]

Hi all

Next week is our big week! Hope to see you all there, here are some heat
sessions/forums for you in Sydney Summit.

For any users and operators who use heat directly or indirectly(like people
who use Magnum/Sahara/Tacker) are welcome to join us for ops and users
feedback forum, we really appreciated for any kind of help and feedbacks.
So heat and other projects that relative to heat can know any issues or
required for improvement exists.

For anyone who would like to see if you could help on contributing in any
way, or you're looking for better knowledge of developing heat, please join
us in our Onboarding session.

And last but not least, please join our project update session for some key
information about what we done for pike and what's plan for queens.

All detail information:

Heat - Project Onboarding
Mon 6, 11:35am - 12:15pm Sydney Convention and Exhibition Centre - Level 4
- C4.7 

Heat - Project Update
Tue 7, 5:00pm - 5:20pm Sydney Convention and Exhibition Centre - Level 3
Convention Center - C3.2


Heat ops and users feedback
Wed 8, 4:30pm - 5:10pm Sydney Convention and Exhibition Centre - Level 4 -
C4.10 


There also a lot of Orchestration relative sessions, so feel free to pick
your favorites.
-- 
May The Force of OpenStack Be With You,

*Rico Lin*irc: ricolin
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators