[Openstack-operators] #PERSONAL# Re: Can single node devstack OpenStack installation have VM migration

[Abhishek Talwar]

Hi Saju,It
 is on KVM. I had tried on setting up a multinode environment with a 
controller, network and 2 compute nodes. But I am facing issues in that.
 Actually, one of the compute's is able to boot a VM and the VM goes to 
Active state. While on the other when I try to boot a VM it stay in 
scheduling state only. Also if I try to migrate the Active VM from 1 
compute to other it gives me an error and the VM is left in error state.So
 I thought of trying it on single-node kilo openstack, where I noticed 
that we have only 1 compute host in single-node setups but then also the
 VM gets migrated. So my question was where does the VM gets migrated 
when we don't have another compute host. RegardsAbhishek-Saju M  wrote: -To: Abhishek Talwar From: Saju M Date: 05/27/2015 10:43AMCc: openstack-operators@lists.openstack.org, "Kris G. Lindgren" , David Medberry Subject: Re: [Openstack-operators] Can single node devstack OpenStack installation have VM migrationHi Abhishek,
Anyway, You are planning to work on VM migration. So it is better to setup multinode environment. Where is your single node setup ? Is it on KVM or Virtualbox VM?
On May 27, 2015 10:33 AM, "Abhishek Talwar"  wrote:Hi,But this link talks about only resizing in single node. I was talking about VM migration in single node ?So how does this relates to VM migration ?-medbe...@gmail.com wrote: -To: "Kris G. Lindgren" From: David Medberry Sent by: medbe...@gmail.comDate: 05/27/2015 10:22AMCc: Abhishek Talwar , "openstack-operators@lists.openstack.org" Subject: Re: [Openstack-operators] Can single node devstack OpenStack installation have VM migrationGood info Kris. I've never used/modified that setting. I learn something (lots actually) every day.On Tue, May 26, 2015 at 10:19 AM, Kris G. Lindgren  wrote:
I belive this can be possible by setting the allow_resize_same_host.  More details can be found here: http://www.madorn.com/resize-on-single-compute.html .  I believe the issue Dave is talking about is specifically targeting the same host for resize assuming
 the host can support it in a milti-node setup.  As getting the scheduler to choose the current host in the multihost setup is 95  percent of the battle.

 Original message 
From: David Medberry  
Date: 05/26/2015 4:36 AM (GMT-08:00) 
To: Abhishek Talwar  
Cc: openstack-operators@lists.openstack.org 
Subject: Re: [Openstack-operators] Can single node devstack OpenStack installation have VM migration


No. Providing a mechanism for this is discussed from time to time, but it is not currently available.

All 


=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. 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] Can single node devstack OpenStack installation have VM migration

[Abhishek Talwar]

Hi Saju,It is on KVM. I had tried on setting up a multinode environment with a controller, network and 2 compute nodes. But I am facing issues in that. Actually, one of the compute's is able to boot a VM and the VM goes to Active state. While on the other when I try to boot a VM it stay in scheduling state only. Also if I try to migrate the Active VM from 1 compute to other it gives me an error and the VM is left in error state.So I thought of trying it on single-node kilo openstack, where I noticed that we have only 1 compute host in single-node setups but then also the VM gets migrated. So my question was where does the VM gets migrated when we don't have another compute host. RegardsAbhishek-Saju M  wrote: -To: Abhishek Talwar From: Saju M Date: 05/27/2015 10:43AMCc: openstack-operators@lists.openstack.org, "Kris G. Lindgren" , David Medberry Subject: Re: [Openstack-operators] Can single node devstack OpenStack installation have VM migrationHi Abhishek,
Anyway, You are planning to work on VM migration. So it is better to setup multinode environment. Where is your single node setup ? Is it on KVM or Virtualbox VM?
On May 27, 2015 10:33 AM, "Abhishek Talwar"  wrote:Hi,But this link talks about only resizing in single node. I was talking about VM migration in single node ?So how does this relates to VM migration ?-medbe...@gmail.com wrote: -To: "Kris G. Lindgren" From: David Medberry Sent by: medbe...@gmail.comDate: 05/27/2015 10:22AMCc: Abhishek Talwar , "openstack-operators@lists.openstack.org" Subject: Re: [Openstack-operators] Can single node devstack OpenStack installation have VM migrationGood info Kris. I've never used/modified that setting. I learn something (lots actually) every day.On Tue, May 26, 2015 at 10:19 AM, Kris G. Lindgren  wrote:
I belive this can be possible by setting the allow_resize_same_host.  More details can be found here: http://www.madorn.com/resize-on-single-compute.html .  I believe the issue Dave is talking about is specifically targeting the same host for resize assuming
 the host can support it in a milti-node setup.  As getting the scheduler to choose the current host in the multihost setup is 95  percent of the battle.

 Original message 
From: David Medberry  
Date: 05/26/2015 4:36 AM (GMT-08:00) 
To: Abhishek Talwar  
Cc: openstack-operators@lists.openstack.org 
Subject: Re: [Openstack-operators] Can single node devstack OpenStack installation have VM migration


No. Providing a mechanism for this is discussed from time to time, but it is not currently available.

All 


=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. 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] Can single node devstack OpenStack installation have VM migration

[Saju M]

Hi Abhishek,
Anyway, You are planning to work on VM migration. So it is better to setup
multinode environment. Where is your single node setup ? Is it on KVM or
Virtualbox VM?
On May 27, 2015 10:33 AM, "Abhishek Talwar"  wrote:

> Hi,
>
> But this link talks about only resizing in single node. I was talking
> about VM migration in single node ?
>
> So how does this relates to VM migration ?
>
> -medbe...@gmail.com wrote: -
> To: "Kris G. Lindgren" 
> From: David Medberry
> Sent by: medbe...@gmail.com
> Date: 05/27/2015 10:22AM
> Cc: Abhishek Talwar , "
> openstack-operators@lists.openstack.org" <
> openstack-operators@lists.openstack.org>
> Subject: Re: [Openstack-operators] Can single node devstack OpenStack
> installation have VM migration
>
> Good info Kris. I've never used/modified that setting. I learn something
> (lots actually) every day.
>
> On Tue, May 26, 2015 at 10:19 AM, Kris G. Lindgren 
> wrote:
>
>>  I belive this can be possible by setting the allow_resize_same_host.
>> More details can be found here:
>> http://www.madorn.com/resize-on-single-compute.html .  I believe the
>> issue Dave is talking about is specifically targeting the same host for
>> resize assuming the host can support it in a milti-node setup.  As getting
>> the scheduler to choose the current host in the multihost setup is 95
>>  percent of the battle.
>>
>>  Original message 
>> From: David Medberry 
>> Date: 05/26/2015 4:36 AM (GMT-08:00)
>> To: Abhishek Talwar 
>> Cc: openstack-operators@lists.openstack.org
>> Subject: Re: [Openstack-operators] Can single node devstack OpenStack
>> installation have VM migration
>>
>> No. Providing a mechanism for this is discussed from time to time, but it
>> is not currently available.
>>
>> All
>>
>
>  =-=-=
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. 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] Can single node devstack OpenStack installation have VM migration

[Abhishek Talwar]

Hi,But this link talks about only resizing in single node. I was talking about VM migration in single node ?So how does this relates to VM migration ?-medbe...@gmail.com wrote: -To: "Kris G. Lindgren" From: David Medberry Sent by: medbe...@gmail.comDate: 05/27/2015 10:22AMCc: Abhishek Talwar , "openstack-operators@lists.openstack.org" Subject: Re: [Openstack-operators] Can single node devstack OpenStack installation have VM migrationGood info Kris. I've never used/modified that setting. I learn something (lots actually) every day.On Tue, May 26, 2015 at 10:19 AM, Kris G. Lindgren  wrote:




I belive this can be possible by setting the allow_resize_same_host.  More details can be found here: http://www.madorn.com/resize-on-single-compute.html .  I believe the issue Dave is talking about is specifically targeting the same host for resize assuming
 the host can support it in a milti-node setup.  As getting the scheduler to choose the current host in the multihost setup is 95  percent of the battle.

 Original message 
From: David Medberry  
Date: 05/26/2015 4:36 AM (GMT-08:00) 
To: Abhishek Talwar  
Cc: openstack-operators@lists.openstack.org 
Subject: Re: [Openstack-operators] Can single node devstack OpenStack installation have VM migration


No. Providing a mechanism for this is discussed from time to time, but it is not currently available.

All 






=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you



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

[Openstack-operators] VM migration in OpenStack kilo

[Abhishek Talwar]

Hi Folks,I have a doubt regarding VM migration in single-node Openstack kilo installation. As all the services run on a single host in single node installation and we have only 1 available compute host, so how does the VM get migrated and where does it get migrated because we do not have another compute host available ?Kindly provide some information on this. RegardsAbhishek Talwar
=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you



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

[Openstack-operators] VM migration in OpenStack kil

[Abhishek Talwar]

Hi Folks,I have a doubt regarding VM migration in single-node Openstack kilo installation. As all the services run on a single host in single node installation and we have only 1 available compute host, so how does the VM get migrated and where does it get migrated because we do not have another compute host available ?Kindly provide some information on this. 
=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you



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

Re: [Openstack-operators] Can single node devstack OpenStack installation have VM migration

[David Medberry]

Good info Kris. I've never used/modified that setting. I learn something
(lots actually) every day.

On Tue, May 26, 2015 at 10:19 AM, Kris G. Lindgren 
wrote:

>  I belive this can be possible by setting the allow_resize_same_host.
> More details can be found here:
> http://www.madorn.com/resize-on-single-compute.html .  I believe the
> issue Dave is talking about is specifically targeting the same host for
> resize assuming the host can support it in a milti-node setup.  As getting
> the scheduler to choose the current host in the multihost setup is 95
>  percent of the battle.
>
>  Original message 
> From: David Medberry 
> Date: 05/26/2015 4:36 AM (GMT-08:00)
> To: Abhishek Talwar 
> Cc: openstack-operators@lists.openstack.org
> Subject: Re: [Openstack-operators] Can single node devstack OpenStack
> installation have VM migration
>
> No. Providing a mechanism for this is discussed from time to time, but it
> is not currently available.
>
> All
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [openstack-dev] [App-Catalog] Planning/working session Wednesday in Vancouver

[Christopher Aedo]

On Tue, May 26, 2015 at 9:22 PM, Keith Bray  wrote:
> I am interested in getting more involved.  Is there any effort already in
> place to run this like a regular project, with IRC meetings, etc.?  What
> are the channels, etc., by which I can get involved.

Keith, glad to hear it!

You can reference a message sent last week for details on the next
steps[1].  The intention is definitely to run this like a regular
project, and the first step is to get responses from those interested
in joining IRC meetings.

Looking forward to working with you on this!

[1]: http://lists.openstack.org/pipermail/openstack-dev/2015-May/064624.html

-Christopher

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

Re: [Openstack-operators] Can single node devstack OpenStack installation have VM migration

[Abhishek Talwar]

Hi,But in the kilo release, if I do a single node devstack installation there is block and live migration. So how is that possible?As a single-node installation has only 1 compute host so where would the VM get migrated ?-"Kris G. Lindgren"  wrote: -To: David Medberry , Abhishek Talwar	From: "Kris G. Lindgren" Date: 05/26/2015 09:49PMCc: "openstack-operators@lists.openstack.org" Subject: RE: [Openstack-operators] Can single node devstack OpenStack installation have VM migration




I belive this can be possible by setting the allow_resize_same_host.  More details can be found here: http://www.madorn.com/resize-on-single-compute.html .  I believe the issue Dave is talking about is specifically targeting the same host for resize assuming
 the host can support it in a milti-node setup.  As getting the scheduler to choose the current host in the multihost setup is 95  percent of the battle.

 Original message 
From: David Medberry  
Date: 05/26/2015 4:36 AM (GMT-08:00) 
To: Abhishek Talwar  
Cc: openstack-operators@lists.openstack.org 
Subject: Re: [Openstack-operators] Can single node devstack OpenStack installation have VM migration


No. Providing a mechanism for this is discussed from time to time, but it is not currently available.

All 





=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you



___
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-operators][chef] OpenStack+Chef is part of the big tent

[Matt Fischer]

Congrats and welcome!
On May 26, 2015 5:35 PM, "JJ Asghar"  wrote:

> Hey everyone!
>
> I’d like to just drop a note to the list saying thank you and
> congratulations to our general community.
>
> As of 2015-05-26 we’ve been merged into the “big tent”[1] sanctioning us
> as an official OpenStack project.
>
> This is amazing news, and lets keep up the great work!
>
> If you have an questions or thoughts please don’t hesitate to reach out.
>
> [1]: https://review.openstack.org/#/c/175000/
>
>
> Best Regards,
> JJ Asghar
> c: 512.619.0722 t: @jjasghar
>
> ___
> 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

[Openstack-operators] [openstack-dev][openstack-operators][chef] OpenStack+Chef is part of the big tent

[JJ Asghar]

Hey everyone!

I’d like to just drop a note to the list saying thank you and congratulations 
to our general community. 

As of 2015-05-26 we’ve been merged into the “big tent”[1] sanctioning us as an 
official OpenStack project.

This is amazing news, and lets keep up the great work!

If you have an questions or thoughts please don’t hesitate to reach out.

[1]: https://review.openstack.org/#/c/175000/ 


Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [openstack-operators][neutron]:stats on FIPs usage

[Mathieu Gagné]

On 2015-05-26 3:25 PM, Daniel Comnea wrote:
> Hi,
>  
> Can anyone share their thoughts, answers to the below problem/ question
> which i'm sure everyone came across while looking after an Openstack
> environment:
>  
> 
> - As an admin how can you find out the usage of all FIPs available
> to be used/ already in used from the big FIP pool for the entire
> environment?
> - As a user/ admin how can you find out the user of all FIPs
> available to be used/ already in used per project from the total FIP
> quota?
> 

Mike Dorman open-sourced an extension used at GoDaddy to track subnet
usage earlier this month:

http://lists.openstack.org/pipermail/openstack-operators/2015-May/006905.html

I think it could be useful for your first use case.

-- 
Mathieu

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

Re: [Openstack-operators] [openstack-operators][neutron]:stats on FIPs usage

[Sean M. Collins]

Most likely by querying the Nova or Neutron mysql/pgsql database
directly.

-- 
Sean M. Collins

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

Re: [Openstack-operators] [openstack-operators][neutron]:stats on FIPs usage

[Daniel Comnea]

Hi,

Can anyone share their thoughts, answers to the below problem/ question
which i'm sure everyone came across while looking after an Openstack
environment:


> - As an admin how can you find out the usage of all FIPs available to be
> used/ already in used from the big FIP pool for the entire environment?
> - As a user/ admin how can you find out the user of all FIPs available to
> be used/ already in used per project from the total FIP quota?
>



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

Re: [Openstack-operators] [openstack-dev] [glance] [kolla] [magnum] [nova] [neutron] Vancouver Summit Operations Containers Session

[Richard Raseley]

Flavio Percoco wrote:


There's work going on on something called Artifacts[0], which - in a
poorly worded definition - is an enhancement of the current image
model in Glance.

It'll take some time for the full migration to happen but that should
solve your requirement.

[0]
http://specs.openstack.org/openstack/glance-specs/specs/kilo/artifact-repository.html



Thank you for bringing that to my attention, this looks like it solves 
the issue we outlined - very exciting. =]


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

Re: [Openstack-operators] Can single node devstack OpenStack installation have VM migration

[Kris G. Lindgren]

I belive this can be possible by setting the allow_resize_same_host.  More 
details can be found here: http://www.madorn.com/resize-on-single-compute.html 
.  I believe the issue Dave is talking about is specifically targeting the same 
host for resize assuming the host can support it in a milti-node setup.  As 
getting the scheduler to choose the current host in the multihost setup is 95  
percent of the battle.

 Original message 
From: David Medberry 
Date: 05/26/2015 4:36 AM (GMT-08:00)
To: Abhishek Talwar 
Cc: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] Can single node devstack OpenStack 
installation have VM migration

No. Providing a mechanism for this is discussed from time to time, but it is 
not currently available.

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

Re: [Openstack-operators] Neutron HA With VRRP (2 Master Nodes, Bogus VRRP packet)

[Eren Türkay]

On 26-05-2015 17:12, Assaf Muller wrote:
> I'd install them via the same tool, make sure the outcome is the same Neutron
> code on both nodes with the same patches applied, recreate the routers 
> entirely
> and see what happens. If it works, work from there.

Thank you for your response! I will try with the exact same code on both
neutron servers. I wasn't aware that minor version could affect this behavior.
I will probably go for ubuntu 14.04 with cloudarchive repositories for neutron
servers (version 2.3.8).

Regards,

-- 
Eren Türkay, System Administrator
https://skyatlas.com/ | +90 850 885 0357

Yildiz Teknik Universitesi Davutpasa Kampusu
Teknopark Bolgesi, D2 Blok No:107
Esenler, Istanbul Pk.34220



signature.asc
Description: OpenPGP digital signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [Large Deployers Team] neutron ask for network segments

[Matt Van Winkle]

From: Kyle Mestery mailto:mest...@mestery.com>>
Date: Tuesday, May 26, 2015 8:56 AM


On Fri, May 22, 2015 at 1:58 PM, Mike Dorman 
mailto:mdor...@godaddy.com>> wrote:
Kris and I along with Belmiro drafted up a description and ask to Neutron about 
the network segments topic.  We just put it at the end of the etherpad, others 
can review:

https://etherpad.openstack.org/p/YVR-ops-large-deployments

(In the "Feedback to Neutron team..." section.)

Yes, thanks for taking this one guys!  Great summary.  The next step would have 
been to take it to the lists, but looks like Kyle already found us. :)



Thanks for writing this up Mike. I heard this request for a "segment" a few 
times last week, especially in regards to cells support in Neutron. I've filed 
a bug (and tagged it as "rfe") [1]. Thanks for the feedback, we'll see what we 
can do for this in Liberty!

Kyle

[1] https://bugs.launchpad.net/neutron/+bug/1458890

Thanks, Kyle!  We started this conversation at the  Large Deployments meeting 
around Neutron and Cells from our side too.  What we realized was that we all 
had slightly different network segmentation with respect to cells, but that was 
the common concern - provider networks being scoped at some level smaller than 
the overall network and items like overlays and such.

We really appreciate you picking this up and helping push it forward.  We have 
monthly team meetings, so if you need regular feedback, let us know and we can 
slot an agenda items for any topics you need.  Also, you are welcome to join us.

Thanks!
Matt




___
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] Neutron HA With VRRP (2 Master Nodes, Bogus VRRP packet)

[Assaf Muller]

Comments in-line.

- Original Message -
> On 26-05-2015 16:46, Assaf Muller wrote:
> > Are you running the same version of the code on both nodes?
> 
> For keepalived, yes. For neutron, no. First node is deployed using Mirantis
> Fuel. Apparently, neutron --version reports 2.3.9. The second node is
> deployed
> using cloudarchive repository (on ubuntu 14.04) and neutron --version reports
> 2.3.8. I'm not sure about the patches that mirantis applies.

OK looking at the generated keepalived.conf I suspected the nodes were using
different Neutron versions. Yes, this could have an impact.

>
> Does this minor difference affect the outcome?
Yes. There were changed in this area between those two versions.

> Should I try installing the
> second node using mirantis repositories or completely isolate neutron nodes
> and
> deploy them using ubuntu cloudarchive repository?

I'd install them via the same tool, make sure the outcome is the same Neutron
code on both nodes with the same patches applied, recreate the routers entirely
and see what happens. If it works, work from there.

> 
> Regards,
> Eren
> 
> --
> Eren Türkay, System Administrator
> https://skyatlas.com/ | +90 850 885 0357
> 
> Yildiz Teknik Universitesi Davutpasa Kampusu
> Teknopark Bolgesi, D2 Blok No:107
> Esenler, Istanbul Pk.34220
> 
> 

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

Re: [Openstack-operators] Neutron HA With VRRP (2 Master Nodes, Bogus VRRP packet)

[Eren Türkay]

On 26-05-2015 16:46, Assaf Muller wrote:
> Are you running the same version of the code on both nodes?

For keepalived, yes. For neutron, no. First node is deployed using Mirantis
Fuel. Apparently, neutron --version reports 2.3.9. The second node is deployed
using cloudarchive repository (on ubuntu 14.04) and neutron --version reports
2.3.8. I'm not sure about the patches that mirantis applies.

Does this minor difference affect the outcome? Should I try installing the
second node using mirantis repositories or completely isolate neutron nodes and
deploy them using ubuntu cloudarchive repository?

Regards,
Eren

-- 
Eren Türkay, System Administrator
https://skyatlas.com/ | +90 850 885 0357

Yildiz Teknik Universitesi Davutpasa Kampusu
Teknopark Bolgesi, D2 Blok No:107
Esenler, Istanbul Pk.34220



signature.asc
Description: OpenPGP digital signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [Large Deployers Team] neutron ask for network segments

[Kyle Mestery]

On Fri, May 22, 2015 at 1:58 PM, Mike Dorman  wrote:

>   Kris and I along with Belmiro drafted up a description and ask to
> Neutron about the network segments topic.  We just put it at the end of the
> etherpad, others can review:
>
>  https://etherpad.openstack.org/p/YVR-ops-large-deployments
>
>  (In the “Feedback to Neutron team…” section.)
>
>
Thanks for writing this up Mike. I heard this request for a "segment" a few
times last week, especially in regards to cells support in Neutron. I've
filed a bug (and tagged it as "rfe") [1]. Thanks for the feedback, we'll
see what we can do for this in Liberty!

Kyle

[1] https://bugs.launchpad.net/neutron/+bug/1458890


>
> ___
> 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] Monitoring and Tools Working Group

[Klein, Bradley]

Thanks for the notes and moderating Graeme -- look forward to meeting on a
bi-weekly basis to stay connected!

On 5/24/15, 4:12 PM, "Graeme Gillies"  wrote:

>Hi,
>
>Just wanted to provide a quick recap the Monitoring and Ops Tools
>session from Summit.
>
>We had good attendance and a lot of people had things to share, things
>they were interested in, and challenges they faced. As these topics are
>a lot more than can be covered by one session, a continuous working
>group was agreed to be setup by those who are interested.
>
>A coverage of almost all what was covered including what was talked
>about, what people are doing/what tools they are using, and what
>problems people are looking at with their current tooling is available
>in the etherpad at
>
>https://etherpad.openstack.org/p/YVR-ops-tools
>
>If you are interested in helping out with or participating in the
>regular Monitoring/Ops Tools discussions, please feel free to leave your
>name in the section at the bottom of the etherpad.
>
>As always, feel free to continue discussion about any and all of these
>topics on this list.
>
>Regards,
>
>Graeme
>
>--
>Graeme Gillies
>Principal Systems Administrator
>Openstack Infrastructure
>Red Hat Australia
>
>___
>OpenStack-operators mailing list
>OpenStack-operators@lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


This E-mail and any of its attachments may contain Time Warner Cable 
proprietary information, which is privileged, confidential, or subject to 
copyright belonging to Time Warner Cable. This E-mail is intended solely for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient of this E-mail, you are hereby notified that any 
dissemination, distribution, copying, or action taken in relation to the 
contents of and attachments to this E-mail is strictly prohibited and may be 
unlawful. If you have received this E-mail in error, please notify the sender 
immediately and permanently delete the original and any copy of this E-mail and 
any printout.

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

Re: [Openstack-operators] Neutron HA With VRRP (2 Master Nodes, Bogus VRRP packet)

[Assaf Muller]

Are you running the same version of the code on both nodes?

- Original Message -
> On 26-05-2015 11:15, Eren Türkay wrote:
> > May 26 10:54:15 neutron-ha-2 Keepalived_vrrp[20144]: ip address associated
> > with
> > VRID not present in received packet : 169.254.0.1
> > May 26 10:54:15 neutron-ha-2 Keepalived_vrrp[20144]: one or more VIP
> > associated
> > with VRID mismatch actual MASTER advert
> > May 26 10:54:15 neutron-ha-2 Keepalived_vrrp[20144]: bogus VRRP packet
> > received
> > on ha-38ff51c5-f0 !!!
> > May 26 10:54:15 neutron-ha-2 Keepalived_vrrp[20144]: VRRP_Instance(VR_1)
> > Dropping received VRRP packet...
> 
> I guess I made some progress. I manually built keepalived.conf. With the
> settings below, keepalived is working without a problem. I added both IP
> addresses (internal HA address and tenant router ip) to vrrp_addresses
> section.
> Master/backup switch is OK, when link goes down, failover happens within a
> reasonable time (20 to 30 seconds). Now, the problem is why keepalived.conf
> is
> deficient on second node and lacking an IP address which causes a problem?
> 
>  BEGIN: keepalived.conf on NODE-1 
> vrrp_sync_group VG_1 {
> group {
> VR_1
> }
> notify_master
> "/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_master.sh"
> notify_backup
> "/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_backup.sh"
> notify_fault
> "/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_fault.sh"
> }
> vrrp_instance VR_1 {
> state BACKUP
> interface ha-b9db8385-67
> virtual_router_id 1
> priority 50
> nopreempt
> advert_int 2
> track_interface {
> ha-b9db8385-67
> }
> virtual_ipaddress {
> 10.30.0.1/24 dev qr-a867fbab-dd
> 169.254.0.1/24 dev ha-b9db8385-67
> }
> virtual_ipaddress_excluded {
> 192.168.92.23/32 dev qg-690ab8d9-81
> 192.168.92.33/16 dev qg-690ab8d9-81
> }
> virtual_routes {
> 0.0.0.0/0 via 192.168.88.1 dev qg-690ab8d9-81
> }
> }
> 
>  END: keepalived.conf on NODE-1 
> 
> 
> 
>  BEGIN: keepalived.conf on NODE-2 
> vrrp_sync_group VG_1 {
> group {
> VR_1
> }
> notify_master
> "/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_master.sh"
> notify_backup
> "/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_backup.sh"
> notify_fault
> "/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_fault.sh"
> }
> vrrp_instance VR_1 {
> state BACKUP
> interface ha-38ff51c5-f0
> virtual_router_id 1
> priority 50
> nopreempt
> advert_int 2
> track_interface {
> ha-38ff51c5-f0
> }
> virtual_ipaddress {
> 10.30.0.1/24 dev qr-a867fbab-dd
> 169.254.0.1/24 dev ha-38ff51c5-f0
> }
> virtual_ipaddress_excluded {
> 192.168.92.23/32 dev qg-690ab8d9-81
> 192.168.92.33/16 dev qg-690ab8d9-81
> fe80::f816:33ff:fe45:26ed/64 dev qr-a867fbab-dd scope link
> fe80::f816:33ff:fee8:fd4b/64 dev qg-690ab8d9-81 scope link
> }
> virtual_routes {
> 0.0.0.0/0 via 192.168.88.1 dev qg-690ab8d9-81
> }
> }
> 
> 
>  END: keepalived.conf on NODE-2 
> 
> --
> Eren Türkay, System Administrator
> https://skyatlas.com/ | +90 850 885 0357
> 
> Yildiz Teknik Universitesi Davutpasa Kampusu
> Teknopark Bolgesi, D2 Blok No:107
> Esenler, Istanbul Pk.34220
> 
> 

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

Re: [Openstack-operators] Openstack Installation with Vlan Interface.

[Anne Gentle]

Hi again -
We have a few docs that may help.

http://docs.openstack.org/admin-guide-cloud/content/section_networking-nova.html

http://docs.openstack.org/kilo/install-guide/install/yum/content/section_nova-networking.html
you'll need to double-check your settings. You haven't said what Operating
system so I'm pointing to RHEL/Fedora though there is also Ubuntu and SUSE
available.

The image itself could cause this error. Depends on what you're trying to
launch. Let us know more info and we'll keep trying.
Thanks,
Anne


On Tue, May 26, 2015 at 7:58 AM, pra devOPS  wrote:

> Hi Anne,
>
> Thanks Installed using both, But when I tired install using nova network
> it says KVM 3181 unhandled error and system got hung.
>
> Thanks,
> siva
>
> On Mon, May 25, 2015 at 11:30 AM, Anne Gentle <
> annegen...@justwriteclick.com> wrote:
>
>> I'm not sure if this is relevant, but the service may be using Linux
>> namespaces, so the interfaces won't be visible when using ifconfig. [1]
>>
>> Also you didn't say if you are using OVS or Linux bridge? Try some of
>> these scenarios to see if it gives you ideas. [2]
>>
>> 1.
>> http://docs.openstack.org/admin-guide-cloud/content/install_neutron-l3.html
>> 2. http://docs.openstack.org/networking-guide/deploy.html
>>
>> On Mon, May 25, 2015 at 10:56 AM, pra devOPS 
>> wrote:
>>
>>> All:
>>>
>>>
>>> I am having problem settinup the network on openstack wiht ml2 plugin.
>>>
>>> Below is my configuration.
>>>
>>> I have a vlan interface which has a IP 1.2.3.4.
>>>
>>> and I have a phsysical interface which is assocaited to that box (that
>>> does not have an IP).
>>>
>>>
>>> Below is How they look like
>>>
>>> VLAN1 (VLAN )  Physical Device Configuration
>>>  --
>>> VLAN=yes TYPE=Ethernet
>>> TYPE=Vlan BOOTPROTO=dhcp
>>> PHYSDEV=phynet1 DEFROUTE=yes
>>> VLAN_ID=1 PEERDNS=yes
>>> REORDER_HDR=0 PEERROUTES=yes
>>> BOOTPROTO=static IPV4_FAILURE_FATAL=no
>>> DOMAIN=eng.myorg.com IPV6INIT=yes
>>> DEFROUTE=yes IPV6_AUTOCONF=yes
>>> IPV4_FAILURE_FATAL=no IPV6_DEFROUTE=yes
>>> IPV6INIT=no IPV6_PEERDNS=yes
>>> IPV6_AUTOCONF=yes IPV6_PEERROUTES=yes
>>> IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no
>>> IPV6_FAILURE_FATAL=no NAME=phynet1
>>> NAME=VLAN1 UUID=5ba6c8d1-8fe7-3fec-ae8c-ad67081547dc
>>> UUID=9cbf88dc-456c-1234-9876-12bece795678 DEVICE=phynet1
>>> ONBOOT=yes ONBOOT=no
>>> DEVICE=MyVLAN1
>>> IPV6_PEERDNS=yes
>>> IPV6_PEERROUTES=yes
>>> IPADDR=1.2.3.4
>>> PREFIX=32
>>> GATEWAY=1.2.3.1
>>> DNS1=1.2.9.5
>>> PEERDNS=yes
>>> PEERROUTES=yes
>>>
>>>
>>>
>>> I added the br-ex and br-int , And added port VLAN1  to br-ex.
>>>
>>> But I dont see the br-ex and br-int interfaces when I do ifconfig.
>>>
>>> Can somebody advice how to setup the network on openStack with above
>>> settings/.
>>>
>>> I am kind of stuck.
>>>
>>> Thanks,
>>> S
>>>
>>> ___
>>> OpenStack-operators mailing list
>>> OpenStack-operators@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>>
>>
>>
>> --
>> Anne Gentle
>> annegen...@justwriteclick.com
>>
>
>


-- 
Anne Gentle
annegen...@justwriteclick.com
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Can single node devstack OpenStack installation have VM migration

[David Medberry]

No. Providing a mechanism for this is discussed from time to time, but it
is not currently available.
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Neutron HA With VRRP (2 Master Nodes, Bogus VRRP packet)

[Eren Türkay]

On 26-05-2015 11:15, Eren Türkay wrote:
> May 26 10:54:15 neutron-ha-2 Keepalived_vrrp[20144]: ip address associated 
> with
> VRID not present in received packet : 169.254.0.1
> May 26 10:54:15 neutron-ha-2 Keepalived_vrrp[20144]: one or more VIP 
> associated
> with VRID mismatch actual MASTER advert
> May 26 10:54:15 neutron-ha-2 Keepalived_vrrp[20144]: bogus VRRP packet 
> received
> on ha-38ff51c5-f0 !!!
> May 26 10:54:15 neutron-ha-2 Keepalived_vrrp[20144]: VRRP_Instance(VR_1)
> Dropping received VRRP packet...

I guess I made some progress. I manually built keepalived.conf. With the
settings below, keepalived is working without a problem. I added both IP
addresses (internal HA address and tenant router ip) to vrrp_addresses section.
Master/backup switch is OK, when link goes down, failover happens within a
reasonable time (20 to 30 seconds). Now, the problem is why keepalived.conf is
deficient on second node and lacking an IP address which causes a problem?

 BEGIN: keepalived.conf on NODE-1 
vrrp_sync_group VG_1 {
group {
VR_1
}
notify_master
"/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_master.sh"
notify_backup
"/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_backup.sh"
notify_fault
"/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_fault.sh"
}
vrrp_instance VR_1 {
state BACKUP
interface ha-b9db8385-67
virtual_router_id 1
priority 50
nopreempt
advert_int 2
track_interface {
ha-b9db8385-67
}
virtual_ipaddress {
10.30.0.1/24 dev qr-a867fbab-dd
169.254.0.1/24 dev ha-b9db8385-67
}
virtual_ipaddress_excluded {
192.168.92.23/32 dev qg-690ab8d9-81
192.168.92.33/16 dev qg-690ab8d9-81
}
virtual_routes {
0.0.0.0/0 via 192.168.88.1 dev qg-690ab8d9-81
}
}

 END: keepalived.conf on NODE-1 



 BEGIN: keepalived.conf on NODE-2 
vrrp_sync_group VG_1 {
group {
VR_1
}
notify_master
"/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_master.sh"
notify_backup
"/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_backup.sh"
notify_fault
"/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_fault.sh"
}
vrrp_instance VR_1 {
state BACKUP
interface ha-38ff51c5-f0
virtual_router_id 1
priority 50
nopreempt
advert_int 2
track_interface {
ha-38ff51c5-f0
}
virtual_ipaddress {
10.30.0.1/24 dev qr-a867fbab-dd
169.254.0.1/24 dev ha-38ff51c5-f0
}
virtual_ipaddress_excluded {
192.168.92.23/32 dev qg-690ab8d9-81
192.168.92.33/16 dev qg-690ab8d9-81
fe80::f816:33ff:fe45:26ed/64 dev qr-a867fbab-dd scope link
fe80::f816:33ff:fee8:fd4b/64 dev qg-690ab8d9-81 scope link
}
virtual_routes {
0.0.0.0/0 via 192.168.88.1 dev qg-690ab8d9-81
}
}


 END: keepalived.conf on NODE-2 

-- 
Eren Türkay, System Administrator
https://skyatlas.com/ | +90 850 885 0357

Yildiz Teknik Universitesi Davutpasa Kampusu
Teknopark Bolgesi, D2 Blok No:107
Esenler, Istanbul Pk.34220



signature.asc
Description: OpenPGP digital signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Can single node devstack OpenStack installation have VM migration

[Abhishek Talwar]

Hi Folks,I am working on the concept of migration in Openstack. I am working on single node devstack installation of Openstack Juno. I wanted to know if we can migrate VM from one host to other in single node installations too as there is a command in nova to do so.I know migrations are achievable in multi-node installations but are the same applicable for Single-node installations too ?Thanks and RegardsAbhishek Talwar
=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you



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

[Openstack-operators] Neutron HA With VRRP (2 Master Nodes, Bogus VRRP packet)

[Eren Türkay]

Hello folks,

I'm trying to use HA with VRRP using keepalived under Juno release. This is a
VLAN setup using ML2 plugin and openvswitch.

I've setup second neutron node and added ha_* configuration parameters. When I
create a new router, I see that it's created on both network nodes. However, it
seems that keepalived cannot select master nodes as both nodes are seen as
"master".

I debugged the problem a bit and came to conclusion that VRRP messages are
correctly sent (with tcpdump). The first node announces that it has the
floating and internal tenant network ip (router ip). Second node also announces
its virtual ip written in keepalived.conf (169.254.0.1). But in the second
node, I see the following message:

May 26 10:54:15 neutron-ha-2 Keepalived_vrrp[20144]: ip address associated with
VRID not present in received packet : 169.254.0.1
May 26 10:54:15 neutron-ha-2 Keepalived_vrrp[20144]: one or more VIP associated
with VRID mismatch actual MASTER advert
May 26 10:54:15 neutron-ha-2 Keepalived_vrrp[20144]: bogus VRRP packet received
on ha-38ff51c5-f0 !!!
May 26 10:54:15 neutron-ha-2 Keepalived_vrrp[20144]: VRRP_Instance(VR_1)
Dropping received VRRP packet...

Indeed, 169.254.0.1 which is present in the second node as virtual ip, is not
announced (or present) in the VRRP message sent from the first node. The
message from the first node only contains router ip address for the tenant
network.

It seems that there is a known bug for neutron with HA setup *if* l2population
is enabled. However, I do not have l2population enabled (it's explicitly
disabled on plugin.ini): https://bugs.launchpad.net/neutron/+bug/1365476

There is a patch [0] for this but it's against master. Accordingly to LP bug
report, it isn't going to be backported to Juno release. Is this LP bug and
patch related to this issue?

I am attaching keepalived.conf files from both of the nodes. The current state
is that those two node states are "master" and I see the "bogus vrrp packet"
error in the second node. There is no backup node and the cluster isn't
functioning.

Has anyone successfully installed HA setup with VRRP? I gladly appreciate any
help regarding to this issue.

Note: keepalived v1.2.16 (05/25,2015) is used in both nodes.

[0] https://review.openstack.org/#/c/141114/


 BEGIN: keepalived.conf on NODE-1 
vrrp_sync_group VG_1 {
group {
VR_1
}
notify_master
"/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_master.sh"
notify_backup
"/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_backup.sh"
notify_fault
"/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_fault.sh"
}
vrrp_instance VR_1 {
state BACKUP
interface ha-b9db8385-67
virtual_router_id 1
priority 50
nopreempt
advert_int 2
track_interface {
ha-b9db8385-67
}
virtual_ipaddress {
10.30.0.1/24 dev qr-a867fbab-dd
}
virtual_ipaddress_excluded {
192.168.92.23/32 dev qg-690ab8d9-81
192.168.92.33/16 dev qg-690ab8d9-81
}
virtual_routes {
0.0.0.0/0 via 192.168.88.1 dev qg-690ab8d9-81
}

 END: keepalived.conf on NODE-1 

 BEGIN: keepalived.conf on NODE-2 
vrrp_sync_group VG_1 {
group {
VR_1
}
notify_master
"/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_master.sh"
notify_backup
"/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_backup.sh"
notify_fault
"/var/lib/neutron/ha_confs/93b94981-01ac-4e59-8718-5103b867f3dd/notify_fault.sh"
}
vrrp_instance VR_1 {
state BACKUP
interface ha-38ff51c5-f0
virtual_router_id 1
priority 50
nopreempt
advert_int 2
track_interface {
ha-38ff51c5-f0
}
virtual_ipaddress {
169.254.0.1/24 dev ha-38ff51c5-f0
}
virtual_ipaddress_excluded {
10.30.0.1/24 dev qr-a867fbab-dd
192.168.92.23/32 dev qg-690ab8d9-81
192.168.92.33/16 dev qg-690ab8d9-81
fe80::f816:33ff:fe45:26ed/64 dev qr-a867fbab-dd scope link
fe80::f816:33ff:fee8:fd4b/64 dev qg-690ab8d9-81 scope link
}
virtual_routes {
0.0.0.0/0 via 192.168.88.1 dev qg-690ab8d9-81
}

 END: keepalived.conf on NODE-2 

-- 
Eren Türkay, System Administrator
https://skyatlas.com/ | +90 850 885 0357

Yildiz Teknik Universitesi Davutpasa Kampusu
Teknopark Bolgesi, D2 Blok No:107
Esenler, Istanbul Pk.34220



signature.asc
Description: OpenPGP digital signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators