[Openstack] Making Nova HA summit notes

Mike Scherbakov mihgen at gmail.com
Fri Jul 22 01:06:45 UTC 2011


Vish,
it works for me (didn't go deep enough in testing though) but with some
additions. Did you forget to add this or I'm missing something?

=== modified file
'nova/db/sqlalchemy/migrate_repo/versions/033_ha_network.py'
--- nova/db/sqlalchemy/migrate_repo/versions/033_ha_network.py  2011-07-19
17:00:00 +0000
+++ nova/db/sqlalchemy/migrate_repo/versions/033_ha_network.py  2011-07-21
21:41:28 +0000
@@ -23,6 +23,8 @@

 networks_multi_host = Column('multi_host', Boolean, default=False)

+networks_dhcp_server = Column('dhcp_server', String(255))
+

 def upgrade(migrate_engine):
     meta.bind = migrate_engine
@@ -32,6 +34,7 @@

     networks = Table('networks', meta, autoload=True)
     networks.create_column(networks_multi_host)
+    networks.create_column(networks_dhcp_server)


 def downgrade(migrate_engine):
@@ -42,3 +45,4 @@

     networks = Table('networks', meta, autoload=True)
     networks.drop_column(networks_multi_host)
+    networks.drop_column(networks_dhcp_server)

=== modified file 'nova/db/sqlalchemy/models.py'
--- nova/db/sqlalchemy/models.py        2011-07-21 14:27:20 +0000
+++ nova/db/sqlalchemy/models.py        2011-07-21 21:45:51 +0000
@@ -562,6 +562,7 @@
     vpn_public_port = Column(Integer)
     vpn_private_address = Column(String(255))
     dhcp_start = Column(String(255))
+    dhcp_server = Column(String(255))

     project_id = Column(String(255))
     host = Column(String(255))  # , ForeignKey('hosts.id'))

Thanks,

2011/7/21 Diego Parrilla Santamaría <diego.parrilla.santamaria at gmail.com>

> Awesome Vish. I will give this network option a try!
>
> Diego
>
> --
> Diego Parrilla
> <http://www.stackops.com>*CEO*
> *www.stackops.com | * diego.parrilla at stackops.com** | +34 649 94 43 29 |
> skype:diegoparrilla*
> * <http://www.stackops.com>
> *
>
> *
>
> ******************** ADVERTENCIA LEGAL ********************
> Le informamos, como destinatario de este mensaje, que el correo electrónico
> y las comunicaciones por medio de Internet no permiten asegurar ni
> garantizar la confidencialidad de los mensajes transmitidos, así como
> tampoco su integridad o su correcta recepción, por lo que STACKOPS
> TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
> Si no consintiese en la utilización del correo electrónico o de las
> comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
> conocimiento de manera inmediata. Este mensaje va dirigido, de manera
> exclusiva, a su destinatario y contiene información confidencial y sujeta al
> secreto profesional, cuya divulgación no está permitida por la ley. En caso
> de haber recibido este mensaje por error, le rogamos que, de forma
> inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
> atención y proceda a su eliminación, así como a la de cualquier documento
> adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
> utilización de este mensaje, o de cualquier documento adjunto al mismo,
> cualquiera que fuera su finalidad, están prohibidas por la ley.
>
> ***************** PRIVILEGED AND CONFIDENTIAL ****************
> We hereby inform you, as addressee of this message, that e-mail and
> Internet do not guarantee the confidentiality, nor the completeness or
> proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
> does not assume any liability for those circumstances. Should you not agree
> to the use of e-mail or to communications via Internet, you are kindly
> requested to notify us immediately. This message is intended exclusively for
> the person to whom it is addressed and contains privileged and confidential
> information protected from disclosure by law. If you are not the addressee
> indicated in this message, you should immediately delete it and any
> attachments and notify the sender by reply e-mail. In such case, you are
> hereby notified that any dissemination, distribution, copying or use of this
> message or any attachments, for any purpose, is strictly prohibited by law.
>
>
>
> On Thu, Jul 21, 2011 at 6:24 PM, Vishvananda Ishaya <vishvananda at gmail.com
> > wrote:
>
>> We just recently merged a new HA networking option.  See details in my
>> blog post here:
>>
>> http://unchainyourbrain.com/openstack/13-networking-in-nova
>>
>> <http://unchainyourbrain.com/openstack/13-networking-in-nova>Vish
>>
>> On Jul 20, 2011, at 10:04 PM, Mike Scherbakov wrote:
>>
>> Hi,
>> Thank you for the work on making nova components HA.
>>
>> Did you have a chance to move further in this topic?
>> I especially interested in making nova-network HA and looking for possible
>> active-active implementations,
>> so the downtime of the service would me minimal.
>>
>> Thank you,
>>
>> On Tue, May 3, 2011 at 1:22 PM, Edward Konetzko <
>> konetzed at quixoticagony.com> wrote:
>>
>>> I have attached the slides and Tushar Patil doc on making nova-network ha
>>> along with the etherpad notes on the bottom.
>>>
>>>
>>> I hope to follow this email up later on in the week with plans for a full
>>> reference document based on Cacti.  Thanks for everyone’s participation at
>>> the Summit.
>>>
>>> Thanks
>>> Edward Konetzko
>>>
>>> Etherpad notes
>>>
>>>
>>> This Etherpad is for the
>>> Discussion on Design & Software Considerations for Making Nova HA/Fault
>>> Tolerant
>>> Please put ideas or comments in the appropriate sections
>>>
>>>
>>> Database
>>> - Does zones alleviate the need for HAing the DB?
>>>
>>>
>>>
>>> RabbitMQ
>>> For comparison http://wiki.secondlife.com/**
>>> wiki/Message_Queue_Evaluation_**Notes<http://wiki.secondlife.com/wiki/Message_Queue_Evaluation_Notes>
>>> - Need to update managers to create persistant queues and messages
>>> - XMPP an alternate?
>>> Talk to RabbitMQ devs about
>>> - Long term can we use Burrow?
>>>
>>>
>>> Nova-Network
>>> NTT Data documentation mailed to openstack list for their heartbeat POC
>>> tests
>>> Are there issues running multiple network nodes and assigning the same IP
>>> to mutlple instances?
>>> How about VRRP protocol?
>>>   --> we (NTT) are planning to evaluate VRRP using keepalived or some
>>> other software. Does anyone knows suitable software?
>>>
>>>
>>> Nova-scheduler
>>> Vish said you can run more then one
>>> - Yeah with zones and how the scheduler is structured now, it can
>>>
>>>
>>> Nova-api
>>> Possibliy to run this behind real web server, apache, nginx
>>>
>>>
>>> Nova-volume
>>>
>>> Nova-Objectstore
>>>
>>> Nova-Compute
>>>
>>>
>>> Other ideas
>>> Services should use dns srv records or something to automate service
>>> discovery, this would make running large infrastructures and ipv6
>>> configureation alot easier.
>>> - zeroconf?  -<-- like the idea but anyone can announce anything in
>>> zeroconf it has no idea of a master for security.
>>> Agreed
>>> Look at vrrp and keepalived
>>>
>>>
>>> Take aways
>>> Start Discussion with Rabbitmq
>>> Message Bus needs more investigation
>>> Discussion on how do we make messages have delievery
>>> Give feed back to end user, fail or pass just dont leave state in pending
>>> forever
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to     : openstack at lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>> Mike Scherbakov
>>  _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack at lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack at lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>


-- 
Mike Scherbakov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20110721/79880471/attachment.html>


More information about the Openstack mailing list