Re: [openstack-dev] [Heat][Docker] How to Dockerize your applications with OpenStack Heat in simple steps
Hi Marouen, Just curious to know more on the deployment of dockers with OpenStack like: i) Does any body deployed dockers with OpenStack? ii) What are the common/most widely deployed applications using Dockers containers? Appreciate your inputs. Regards, Balaji.P On Wed, Aug 27, 2014 at 8:00 PM, Marouen Mechtri mechtri.mar...@gmail.com wrote: Hi Thiago, Yes Docker could be used to replace the virtualization layer on the Compute Node, it's the case if we configure Nova to use the Docker Driver. In our case, we are orchestrating Docker in OpenStack via Heat. We used a VM as a docker host for many reasons : - It is a way to economize IP addresses : If the docker host is a physical server, every container needs a floating IP (to be reachable from outside). When the docker host is a VM, we associate one floating IP to it and we can access to containers via binding ports (@VM-floatingIP:container-binding-port). - To achieve stronger isolation and security - To easily integrate docker with existing VM-based management and monitoring tools - We think that Docker and virtualization could also be complementary. Thank you for the question We will update the document to clarify these points. https://github.com/MarouenMechtri/Docker-containers-deployment-with-OpenStack-Heat Regards, Marouen 2014-08-26 21:35 GMT+02:00 Martinx - ジェームズ thiagocmarti...@gmail.com: Hey Stackers! Wait! =) Let me ask something... Why are you guys using Docker within a VM?!?! What is the point of doing such thing?! I thought Docker was here to entirely replace the virtualization layer, bringing a bare metal-cloud, am I right?! Tks! Thiago On 26 August 2014 05:45, Marouen Mechtri mechtri.mar...@gmail.com wrote: Hi Angus, We are not using nova-docker driver to deploy docker containers. In our manual, we are using Heat (thanks to the docker plugin) to deploy docker containers and nova is just used to deploy VM. Inside this VM heat deploy the docker software. The figure below describes the interactions between different components. Regards, Marouen [image: Images intégrées 1] 2014-08-26 0:13 GMT+02:00 Angus Salkeld asalk...@mirantis.com: This seems misleading as there is no description on setting up nova-docker or using the heat docker container. -Angus On Tue, Aug 26, 2014 at 5:56 AM, Marouen Mechtri mechtri.mar...@gmail.com wrote: Hi all, I want to present you our guide for Docker containers deployment with OpenStack Heat. In this guide we dockerize and deploy a lamp application on two containers. https://github.com/MarouenMechtri/OpenStack-Heat-Installation/blob/master/Docker-containers-deployment-with-OpenStack-Heat.rst https://github.com/MarouenMechtri/OpenStack-Heat-Installation/blob/master/OpenStack-Heat-Installation.rst Hope it will be helpful for many people. Please let us know your opinion about it. Regards, Marouen Mechtri ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Openstack on power pc/Freescale linux
Hi Qing, Freescale SoCs like P4080 and T4240 etc are supported for OpenStack as well. We have been using them from OpenStack Diablo release onwards. We demonstrated at ONS 2013, Interop 2013 and China Road Show. Regards, Balaji.P On 23 October 2013 08:57, Qing He qing...@radisys.com wrote: Matt, ** ** Great. Yes, what processor and free scale version you are running on? Do you have something for tryout? ** ** Thanks, Qing ** ** *From:* Matt Riedemann [mailto:mrie...@us.ibm.com] *Sent:* Tuesday, October 22, 2013 8:11 PM *To:* OpenStack Development Mailing List *Subject:* Re: [openstack-dev] [nova] Openstack on power pc/Freescale linux ** ** Yeah, my team does. We're using openvswitch 1.10, qpid 0.22, DB2 10.5 (but MySQL also works). Do you have specific issues/questions? We're working on getting continuous integration testing working for the nova powervm driver in the icehouse release, so you can see some more details about what we're doing with openstack on power in this thread: http://lists.openstack.org/pipermail/openstack-dev/2013-October/016395.html Thanks, *MATT RIEDEMANN* Advisory Software Engineer Cloud Solutions and OpenStack Development -- *Phone:* 1-507-253-7622 | *Mobile:* 1-507-990-1889* E-mail:* mrie...@us.ibm.com [image: IBM] 3605 Hwy 52 N Rochester, MN 55901-1407 United States From:Qing He qing...@radisys.com To:OpenStack Development Mailing List openstack-dev@lists.openstack.org, Date:10/22/2013 07:43 PM Subject:Re: [openstack-dev] [nova] Openstack on power pc/Freescale linux -- Thanks Matt. I’d like know if anyone has tried to run the controller, API server and MySql database, msg queue, etc—the brain of the openstack, on ppc. Qing *From:* Matt Riedemann [mailto:mrie...@us.ibm.com mrie...@us.ibm.com] * Sent:* Tuesday, October 22, 2013 4:17 PM* To:* OpenStack Development Mailing List* Subject:* Re: [openstack-dev] [nova] Openstack on power pc/Freescale linux We run openstack on ppc64 with RHEL 6.4 using the powervm nova virt driver. What do you want to know? Thanks, * MATT RIEDEMANN* Advisory Software Engineer Cloud Solutions and OpenStack Development -- *Phone:* 1-507-253-7622 | *Mobile:* 1-507-990-1889* E-mail:* mrie...@us.ibm.com [image: IBM] 3605 Hwy 52 N Rochester, MN 55901-1407 United States From:Qing He qing...@radisys.com To:OpenStack Development Mailing List openstack-dev@lists.openstack.org, Date:10/22/2013 05:49 PM Subject:[openstack-dev] [nova] Openstack on power pc/Freescale linux -- All, I'm wondering if anyone tried OpenStack on Power PC/ free scale Linux? Thanks, Qing ___ OpenStack-dev mailing list* *OpenStack-dev@lists.openstack.org* *http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev image001.gif___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] [Libvirt] Virtio-Serial support for Nova libvirt driver
Hi Haomai, Thanks for your interest on this. The code check-ins done against the below bp are more specific to Qemu Guest Agent. https://blueprints.launchpad.net/nova/+spec/qemu-guest-agent-support Our requirement is to enable Virtio-Serial Interface to the applications running in VM. Do you have the same requirement? We will share the draft BP on this. Any comments on this approach will be helpful. Regards, Balaji.P On Tue, Sep 24, 2013 at 8:10 PM, Haomai Wang hao...@unitedstack.com wrote: On Sep 24, 2013, at 6:40 PM, P Balaji-B37839 b37...@freescale.com wrote: Hi, Virtio-Serial interface support for Nova - Libvirt is not available now. Some VMs who wants to access the Host may need like running qemu-guest-agent or any proprietary software want to use this mode of communication with Host. Qemu-GA uses virtio-serial communication. We want to propose a blue-print on this for IceHouse Release. Anybody interested on this. Great! We have common interest and I hope we can promote it for IceHouse. BTW, do you have a initial plan or description about it. And I think this bp may invoke. https://blueprints.launchpad.net/nova/+spec/qemu-guest-agent-support Regards, Balaji.P ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Best regards, Haomai Wang, UnitedStack Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Resource URL support for more than two levels
Hi, When compared to Nova URL implementations, It is observed that the Neutron URL support cannot be used for more than TWO levels. Applications which want to add as PLUG-IN may be restricted with this. We want to add support for changes required for supporting more than TWO Levels of URL by adding the support changes required in Core Neutron Files. Any comments/interest in this.? Regards, Balaji.P On Tue, Aug 27, 2013 at 5:04 PM, B Veera-B37207 b37...@freescale.comwrote: Hi, ** ** The current infrastructure provided in Quantum [Grizzly], while building Quantum API resource URL using the base function ‘base.create_resource()’ and RESOURCE_ATTRIBUTE_MAP/SUB_RESOURCE_ATTRIBUTE_MAP, supports only two level URI. Example: GET /lb/pools/pool_id/members/member_id ** ** Some applications may need more than two levels of URL support. Example: GET /lb/pools/pool_id/members/member_id/xyz/xyz_id ** ** If anybody is interested in this, we want to contribute for this as BP and make it upstream. ** ** Regards, Veera. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Access to blueprints
Hi Greg, Specification URL is updated with BP document. Any Comments/Suggestions are most welcome. Regards, Balaji.P On Sat, Aug 17, 2013 at 3:32 AM, Regnier, Greg J greg.j.regn...@intel.comwrote: Hi, ** ** I am logged into Launchpad and I cannot access the url for this blueprint: https://blueprints.launchpad.net/neutron/+spec/nfv-and-network-service-chain-implementation ** ** I noticed I cannot access many of these types of url’s. Is this a problem on my end, or is this truly private information. ** ** Thanks, Greg Regnier ** ** ** ** ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] 答复: Proposal for approving Auto HA development blueprint.
Potential candidate as new service like Ceilometer, Heat etc for OpenStack and provide High Availability of VMs. Good topic to discuss at Summit for implementation post Havana Release. On Tue, Aug 13, 2013 at 12:03 PM, Alex Glikson glik...@il.ibm.com wrote: Agree. Some enhancements to Nova might be still required (e.g., to handle resource reservations, so that there is enough capacity), but the end-to-end framework probably should be outside of existing services, probably talking to Nova, Ceilometer and potentially other components (maybe Cinder, Neutron, Ironic), and 'orchestrating' failure detection, fencing and recovery. Probably worth a discussion at the upcoming summit. Regards, Alex From:Konglingxian konglingx...@huawei.com To:OpenStack Development Mailing List openstack-dev@lists.openstack.org, Date:13/08/2013 07:07 AM Subject:[openstack-dev] 答复: Proposal for approving Auto HA developmentblueprint. -- Hi yongiman: Your idea is good, but I think the auto HA operation is not OpenStack’s business. IMO, Ceilometer offers ‘monitoring’, Nova offers ‘evacuation’, and you can combine them to realize HA operation. So, I’m afraid I can’t understand the specific implementation details very well. Any different opinions? *发件人:* yongi...@gmail.com [mailto:yongi...@gmail.com yongi...@gmail.com] * 发送时间:* 2013年8月12日 20:52* 收件人:* openstack-dev@lists.openstack.org* 主题:* Re: [openstack-dev] Proposal for approving Auto HA development blueprint. Hi, Now, I am developing auto ha operation for vm high availability. This function is all progress automatically. It needs other service like ceilometer. ceilometer monitors compute nodes. When ceilometer detects broken compute node, it send a api call to Nova, nova exposes for auto ha API. When received auto ha call, nova progress auto ha operation. All auto ha enabled VM where are running on broken host are all migrated to auto ha Host which is extra compute node for using only Auto-HA function. Below is my blueprint and wiki page. Wiki page is not yet completed. Now I am adding lots of information for this function. Thanks *https://blueprints.launchpad.net/nova/+spec/vm-auto-ha-when-host-broken*https://blueprints.launchpad.net/nova/+spec/vm-auto-ha-when-host-broken *https://wiki.openstack.org/wiki/Autoha*https://wiki.openstack.org/wiki/Autoha ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] FWaaS: Support for explicit commit
Hi Sumit, So all the other Network Services like LBaaS, VPNaaS as well also has to support implicit and explicit 'Commit' modes for configuration. It is certainly a good idea to support implicit and explicit modes. It is good if all the other network services also follows the same. regards, balaji On Sat, Aug 3, 2013 at 7:13 AM, Sumit Naiksatam sumitnaiksa...@gmail.comwrote: Hi All, In Neutron Firewall as a Service (FWaaS), we currently support an implicit commit mode, wherein a change made to a firewall_rule is propagated immediately to all the firewalls that use this rule (via the firewall_policy association), and the rule gets applied in the backend firewalls. This might be acceptable, however this is different from the explicit commit semantics which most firewalls support. Having an explicit commit operation ensures that multiple rules can be applied atomically, as opposed to in the implicit case where each rule is applied atomically and thus opens up the possibility of security holes between two successive rule applications. So the proposal here is quite simple - * When any changes are made to the firewall_rules (added/deleted/updated), no changes will happen on the firewall (only the corresponding firewall_rule resources are modified). * We will support an explicit commit operation on the firewall resource. Any changes made to the rules since the last commit will now be applied to the firewall when this commit operation is invoked. * A show operation on the firewall will show a list of the currently committed rules, and also the pending changes. Kindly respond if you have any comments on this. Thanks, ~Sumit. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
