[openstack-dev] [networking-sfc] Add extension to DB UT

[Vikash Kumar]

Hi All,

 I have added tap extension for https://blueprints.launchpad.
net/networking-sfc/+spec/sfc-tap-port-pair.

 I wanted to add extension for DB validation. Where should i add the
extension ? I tried adding extension here:

https://github.com/openstack/networking-sfc/blob/master/
networking_sfc/tests/unit/db/test_sfc_db.py#L281

  but seems thats not working.


I have validated the extension on devstack setup and it works as
expected.

   Any pointers ?

Regards,
Vikash
__
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

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

[Vikash Kumar]

On Fri, Jun 16, 2017 at 3:39 PM, Thierry Carrez 
wrote:

> Shake Chen wrote:
> > HI Vikash
> >
> > I think Kolla is suitable for official project for deployment
>
> Deployment tooling is, by nature, opinionated. You just can't enable
> everything and keep it manageable. As long as people will have differing
> opinions on how OpenStack pieces should be deployed, which drivers or
> components should actually be made available, or the level of
> fine-tuning that should be exposed, you will have different deployment
> tools.
>
> "Picking one" won't magically make everyone else stop working on their
> specific vision for it, and suddenly force everyone to focus on a single
> solution. It will, however, hamper open collaboration between
> organizations on alternative approaches.
>

​"Picking one" is not, but having the minimal one (core components) is
what I see in the best interest of Openstack. ​I agree that the
deployment is very opinionated but before some one go for deployment
they need to evaluate few things, get some confidence. Right now,
the only option is either turn to vendors or get the experts to do. Or Am i
missing something and Openstack can be evaluated by any organization
without any hassle ?
Having a minimal deployment software will ease this process and kind of
increase
the audience. I don't see having this will create any conflict or hinder any
collaboration.


> My personal view is that it's a space where we need to let flowers bloom
> and encourage open collaboration. We just need to clean up the garden
> when those flowers don't go anywhere.
>
> --
> 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 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

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

[Vikash Kumar]

I strongly believe Openstack must have any one official project for
deployment whether its Fuel or anything else. Cutting it short, talking to
number of people across industry/academic/government institutions, got a
sense that its necessary that there should be a official tool more than
Devstack for deployment.

Regards,
Vikash

On Fri, Jun 16, 2017 at 2:20 AM, Dean Troyer  wrote:

> On Thu, Jun 15, 2017 at 10:33 AM, Jay Pipes  wrote:
> > I'd fully support the removal of all deployment projects from the
> "official
> > OpenStack projects list".
>
> Nice to hear Jay! :)
>
> It was intentional from the beginning to not be in the deployment
> space, we allowed those projects in (not unanimously IIRC) and most of
> them did not evolve as expected.
>
> I would not mind picking one winner and spending effort making an
> extremely easy, smooth, upgradable install that is The OneTrue
> OpenStack, I do not expect us to ever agree what that will look like
> so it is effectively never going to happen.  We've seen how far
> single-vendor projects have gone, and none of them reached that level.
>
> dt
>
> --
>
> Dean Troyer
> dtro...@gmail.com
>
> __
> 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 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

Re: [openstack-dev] [reno] we need help reviewing patches to reno

[Vikash Kumar]

Hi Doug,

 Will participate in reno reviews.

Regards,
Vikash

*"Without requirements or design, programming is the art of adding bugs to
an empty text file."- Louis Srygley*

On Tue, Jun 6, 2017 at 8:41 PM, Julien Danjou  wrote:

> On Tue, Jun 06 2017, Doug Hellmann wrote:
>
> > I am looking for one or two people interested in learning about how reno
> > works to help with reviews. If you like graph traversal algorithms
> > and/or text processing, have a look at the code in the openstack/reno
> > repository and let me know if you're interested in helping out.
>
> I've added it to my list of watched projects. I'll try to review patches
> as they come in. I use reno and I like it. :)
>
> --
> Julien Danjou
> ;; Free Software hacker
> ;; https://julien.danjou.info
>
> __
> 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 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

Re: [openstack-dev] [vitrage] [nova] [HA] [masakari] VM Heartbeat / Healthcheck Monitoring

[Vikash Kumar]

Thanks Sam , Will sure review it.

On Tue, 30 May 2017, 17:59 Sam P, <sam47pr...@gmail.com> wrote:

> Hi Vikash,
>
>   Greg submit the spec [1] for intrusive instance monitoring.
>   Your review will be highly appreciated..
>  [1] https://review.openstack.org/#/c/469070/
> --- Regards,
> Sampath
>
>
>
> On Sat, May 20, 2017 at 4:49 PM, Vikash Kumar
> <vikash.ku...@oneconvergence.com> wrote:
> > Thanks Sam
> >
> >
> > On Sat, 20 May 2017, 06:51 Sam P, <sam47pr...@gmail.com> wrote:
> >>
> >> Hi Vikash,
> >>  Great... I will add you as reviewer to this spec.
> >>  Thank you..
> >> --- Regards,
> >> Sampath
> >>
> >>
> >>
> >> On Fri, May 19, 2017 at 1:06 PM, Vikash Kumar
> >> <vikash.ku...@oneconvergence.com> wrote:
> >> > Hi Greg,
> >> >
> >> > Please include my email in this spec also. We are also dealing
> with
> >> > HA
> >> > of Virtual Instances (especially for Vendors) and will participate.
> >> >
> >> > On Thu, May 18, 2017 at 11:33 PM, Waines, Greg
> >> > <greg.wai...@windriver.com>
> >> > wrote:
> >> >>
> >> >> Yes I am good with writing spec for this in masakari-spec.
> >> >>
> >> >>
> >> >>
> >> >> Do you use gerrit for this git ?
> >> >>
> >> >> Do you have a template for your specs ?
> >> >>
> >> >>
> >> >>
> >> >> Greg.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> From: Sam P <sam47pr...@gmail.com>
> >> >> Reply-To: "openstack-dev@lists.openstack.org"
> >> >> <openstack-dev@lists.openstack.org>
> >> >> Date: Thursday, May 18, 2017 at 1:51 PM
> >> >> To: "openstack-dev@lists.openstack.org"
> >> >> <openstack-dev@lists.openstack.org>
> >> >> Subject: Re: [openstack-dev] [vitrage] [nova] [HA] [masakari] VM
> >> >> Heartbeat
> >> >> / Healthcheck Monitoring
> >> >>
> >> >>
> >> >>
> >> >> Hi Greg,
> >> >>
> >> >> Thank you Adam for followup.
> >> >>
> >> >> This is new feature for masakari-monitors and think  Masakari can
> >> >>
> >> >> accommodate this feature in  masakari-monitors.
> >> >>
> >> >> From the implementation prospective, it is not that hard to do.
> >> >>
> >> >> However, as you can see in our Boston presentation, Masakari will
> >> >>
> >> >> replace its monitoring parts ( which is masakari-monitors) with,
> >> >>
> >> >> nova-host-alerter, **-process-alerter, and **-instance-alerter. (**
> >> >>
> >> >> part is not defined yet..:p)...
> >> >>
> >> >> Therefore, I would like to save this specifications, and make sure we
> >> >>
> >> >> will not miss  anything in the transformation..
> >> >>
> >> >> Does is make sense to write simple spec for this in masakari-spec
> [1]?
> >> >>
> >> >> So we can discuss about the requirements how to implement it.
> >> >>
> >> >>
> >> >>
> >> >> [1] https://github.com/openstack/masakari-specs
> >> >>
> >> >>
> >> >>
> >> >> --- Regards,
> >> >>
> >> >> Sampath
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> On Thu, May 18, 2017 at 2:29 AM, Adam Spiers <aspi...@suse.com>
> wrote:
> >> >>
> >> >> I don't see any reason why masakari couldn't handle that, but you'd
> >> >>
> >> >> have to ask Sampath and the masakari team whether they would consider
> >> >>
> >> >> that in scope for their roadmap.
> >> >>
> >> >>
> >> >>
> >> >> Waines, Greg <greg.wai...@windriver.com> wrote:
> >> >>
> >> >>
> >> >>
> >> >> Sure.  I can propose a new user story.
> 

Re: [openstack-dev] [vitrage] [nova] [HA] [masakari] VM Heartbeat / Healthcheck Monitoring

[Vikash Kumar]

Thanks Sam

On Sat, 20 May 2017, 06:51 Sam P, <sam47pr...@gmail.com> wrote:

> Hi Vikash,
>  Great... I will add you as reviewer to this spec.
>  Thank you..
> --- Regards,
> Sampath
>
>
>
> On Fri, May 19, 2017 at 1:06 PM, Vikash Kumar
> <vikash.ku...@oneconvergence.com> wrote:
> > Hi Greg,
> >
> > Please include my email in this spec also. We are also dealing with
> HA
> > of Virtual Instances (especially for Vendors) and will participate.
> >
> > On Thu, May 18, 2017 at 11:33 PM, Waines, Greg <
> greg.wai...@windriver.com>
> > wrote:
> >>
> >> Yes I am good with writing spec for this in masakari-spec.
> >>
> >>
> >>
> >> Do you use gerrit for this git ?
> >>
> >> Do you have a template for your specs ?
> >>
> >>
> >>
> >> Greg.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> From: Sam P <sam47pr...@gmail.com>
> >> Reply-To: "openstack-dev@lists.openstack.org"
> >> <openstack-dev@lists.openstack.org>
> >> Date: Thursday, May 18, 2017 at 1:51 PM
> >> To: "openstack-dev@lists.openstack.org"
> >> <openstack-dev@lists.openstack.org>
> >> Subject: Re: [openstack-dev] [vitrage] [nova] [HA] [masakari] VM
> Heartbeat
> >> / Healthcheck Monitoring
> >>
> >>
> >>
> >> Hi Greg,
> >>
> >> Thank you Adam for followup.
> >>
> >> This is new feature for masakari-monitors and think  Masakari can
> >>
> >> accommodate this feature in  masakari-monitors.
> >>
> >> From the implementation prospective, it is not that hard to do.
> >>
> >> However, as you can see in our Boston presentation, Masakari will
> >>
> >> replace its monitoring parts ( which is masakari-monitors) with,
> >>
> >> nova-host-alerter, **-process-alerter, and **-instance-alerter. (**
> >>
> >> part is not defined yet..:p)...
> >>
> >> Therefore, I would like to save this specifications, and make sure we
> >>
> >> will not miss  anything in the transformation..
> >>
> >> Does is make sense to write simple spec for this in masakari-spec [1]?
> >>
> >> So we can discuss about the requirements how to implement it.
> >>
> >>
> >>
> >> [1] https://github.com/openstack/masakari-specs
> >>
> >>
> >>
> >> --- Regards,
> >>
> >> Sampath
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Thu, May 18, 2017 at 2:29 AM, Adam Spiers <aspi...@suse.com> wrote:
> >>
> >> I don't see any reason why masakari couldn't handle that, but you'd
> >>
> >> have to ask Sampath and the masakari team whether they would consider
> >>
> >> that in scope for their roadmap.
> >>
> >>
> >>
> >> Waines, Greg <greg.wai...@windriver.com> wrote:
> >>
> >>
> >>
> >> Sure.  I can propose a new user story.
> >>
> >>
> >>
> >> And then are you thinking of including this user story in the scope of
> >>
> >> what masakari would be looking at ?
> >>
> >>
> >>
> >> Greg.
> >>
> >>
> >>
> >>
> >>
> >> From: Adam Spiers <aspi...@suse.com>
> >>
> >> Reply-To: "openstack-dev@lists.openstack.org"
> >>
> >> <openstack-dev@lists.openstack.org>
> >>
> >> Date: Wednesday, May 17, 2017 at 10:08 AM
> >>
> >> To: "openstack-dev@lists.openstack.org"
> >>
> >> <openstack-dev@lists.openstack.org>
> >>
> >> Subject: Re: [openstack-dev] [vitrage] [nova] [HA] VM Heartbeat /
> >>
> >> Healthcheck Monitoring
> >>
> >>
> >>
> >> Thanks for the clarification Greg.  This sounds like it has the
> >>
> >> potential to be a very useful capability.  May I suggest that you
> >>
> >> propose a new user story for it, along similar lines to this existing
> >>
> >> one?
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> http://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/ha_vm.html
> >>
> >>
> >>
> >> Waines, Greg <gre

[openstack-dev] [neutron-fwaas]Re: Heat Support for FWaaSv2

[Vikash Kumar]

On Fri, May 19, 2017 at 10:54 AM, Vikash Kumar <
vikash.ku...@oneconvergence.com> wrote:

> Hi Team,
>
>Are we planning for Heat support for FWAASV2 ? I see its missing.
>
> --
> Regards,
> Vikash
>



-- 
Regards,
Vikash
__
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

Re: [openstack-dev] [vitrage] [nova] [HA] [masakari] VM Heartbeat / Healthcheck Monitoring

[Vikash Kumar]

Hi Greg,

Please include my email in this spec also. We are also dealing with HA
of Virtual Instances (especially for Vendors) and will participate.

On Thu, May 18, 2017 at 11:33 PM, Waines, Greg 
wrote:

> Yes I am good with writing spec for this in masakari-spec.
>
>
>
> Do you use gerrit for this git ?
>
> Do you have a template for your specs ?
>
>
>
> Greg.
>
>
>
>
>
>
>
> *From: *Sam P 
> *Reply-To: *"openstack-dev@lists.openstack.org"  openstack.org>
> *Date: *Thursday, May 18, 2017 at 1:51 PM
> *To: *"openstack-dev@lists.openstack.org"  openstack.org>
> *Subject: *Re: [openstack-dev] [vitrage] [nova] [HA] [masakari] VM
> Heartbeat / Healthcheck Monitoring
>
>
>
> Hi Greg,
>
> Thank you Adam for followup.
>
> This is new feature for masakari-monitors and think  Masakari can
>
> accommodate this feature in  masakari-monitors.
>
> From the implementation prospective, it is not that hard to do.
>
> However, as you can see in our Boston presentation, Masakari will
>
> replace its monitoring parts ( which is masakari-monitors) with,
>
> nova-host-alerter, **-process-alerter, and **-instance-alerter. (**
>
> part is not defined yet..:p)...
>
> Therefore, I would like to save this specifications, and make sure we
>
> will not miss  anything in the transformation..
>
> Does is make sense to write simple spec for this in masakari-spec [1]?
>
> So we can discuss about the requirements how to implement it.
>
>
>
> [1] https://github.com/openstack/masakari-specs
>
>
>
> --- Regards,
>
> Sampath
>
>
>
>
>
>
>
> On Thu, May 18, 2017 at 2:29 AM, Adam Spiers  wrote:
>
> I don't see any reason why masakari couldn't handle that, but you'd
>
> have to ask Sampath and the masakari team whether they would consider
>
> that in scope for their roadmap.
>
>
>
> Waines, Greg  wrote:
>
>
>
> Sure.  I can propose a new user story.
>
>
>
> And then are you thinking of including this user story in the scope of
>
> what masakari would be looking at ?
>
>
>
> Greg.
>
>
>
>
>
> From: Adam Spiers 
>
> Reply-To: "openstack-dev@lists.openstack.org"
>
> 
>
> Date: Wednesday, May 17, 2017 at 10:08 AM
>
> To: "openstack-dev@lists.openstack.org"
>
> 
>
> Subject: Re: [openstack-dev] [vitrage] [nova] [HA] VM Heartbeat /
>
> Healthcheck Monitoring
>
>
>
> Thanks for the clarification Greg.  This sounds like it has the
>
> potential to be a very useful capability.  May I suggest that you
>
> propose a new user story for it, along similar lines to this existing
>
> one?
>
>
>
>
>
> http://specs.openstack.org/openstack/openstack-user-
> stories/user-stories/proposed/ha_vm.html
>
>
>
> Waines, Greg 
> >
>
> wrote:
>
> Yes that’s correct.
>
> VM Heartbeating / Health-check Monitoring would introduce intrusive /
>
> white-box type monitoring of VMs / Instances.
>
>
>
> I realize this is somewhat in the gray-zone of what a cloud should be
>
> monitoring or not,
>
> but I believe it provides an alternative for Applications deployed in VMs
>
> that do not have an external monitoring/management entity like a VNF
> Manager
>
> in the MANO architecture.
>
> And even for VMs with VNF Managers, it provides a highly reliable
>
> alternate monitoring path that does not rely on Tenant Networking.
>
>
>
> You’re correct, that VM HB/HC Monitoring would leverage
>
> https://wiki.libvirt.org/page/Qemu_guest_agent
>
> that would require the agent to be installed in the images for talking
>
> back to the compute host.
>
> ( there are other examples of similar approaches in openstack ... the
>
> murano-agent for installation, the swift-agent for object store management
> )
>
> Although here, in the case of VM HB/HC Monitoring, via the QEMU Guest
>
> Agent, the messaging path is internal thru a QEMU virtual serial device.
>
> i.e. a very simple interface with very few dependencies ... it’s up and
>
> available very early in VM lifecycle and virtually always up.
>
>
>
> Wrt failure modes / use-cases
>
>
>
> · a VM’s response to a Heartbeat Challenge Request can be as
>
> simple as just ACK-ing,
>
> this alone allows for detection of:
>
>
>
> oa failed or hung QEMU/KVM instance, or
>
>
>
> oa failed or hung VM’s OS, or
>
>
>
> oa failure of the VM’s OS to schedule the QEMU Guest Agent daemon, or
>
>
>
> oa failure of the VM to route basic IO via linux sockets.
>
>
>
> · I have had feedback that this is similar to the virtual hardware
>
> watchdog of QEMU/KVM (
>
> https://libvirt.org/formatdomain.html#elementsWatchdog )
>
>
>
> · However, the VM Heartbeat / Health-check Monitoring
>
>
>
> o   provides a higher-level (i.e. application-level) heartbeating
>
>
>
> §  i.e. if the Heartbeat requests are being 

[openstack-dev] [networking-sfc] pep8 failing

[Vikash Kumar]

Hi Team,

  pep8 is failing in master code. *translation hint helpers *are removed
from LOG messages. Is this purposefully done ? Let me know if it is not,
will change it.

./networking_sfc/db/flowclassifier_db.py:342:13: N531  Log messages require
translation hints!
LOG.info("Deleting a non-existing flow classifier.")
^
./networking_sfc/db/sfc_db.py:383:13: N531  Log messages require
translation hints!
LOG.info("Deleting a non-existing port chain.")
^
./networking_sfc/db/sfc_db.py:526:13: N531  Log messages require
translation hints!
LOG.info("Deleting a non-existing port pair.")
^
./networking_sfc/db/sfc_db.py:658:13: N531  Log messages require
translation hints!
LOG.info("Deleting a non-existing port pair group.")
^
./networking_sfc/services/flowclassifier/driver_manager.py:38:9: N531  Log
messages require translation hints!
LOG.info("Configured Flow Classifier drivers: %s", names)
^
./networking_sfc/services/flowclassifier/driver_manager.py:44:9: N531  Log
messages require translation hints!
LOG.info("Loaded Flow Classifier drivers: %s",
^
./networking_sfc/services/flowclassifier/driver_manager.py:80:9: N531  Log
messages require translation hints!
LOG.info("Registered Flow Classifier drivers: %s",
^
./networking_sfc/services/flowclassifier/driver_manager.py:87:13: N531  Log
messages require translation hints!
LOG.info("Initializing Flow Classifier driver '%s'",
^
./networking_sfc/services/flowclassifier/driver_manager.py:107:17: N531
Log messages require translation hints!
LOG.error(
^
./networking_sfc/services/flowclassifier/plugin.py:63:17: N531  Log
messages require translation hints!
LOG.error("Create flow classifier failed, "
^
./networking_sfc/services/flowclassifier/plugin.py:87:17: N531  Log
messages require translation hints!
LOG.error("Update flow classifier failed, "
^
./networking_sfc/services/flowclassifier/plugin.py:102:17: N531  Log
messages require translation hints!
LOG.error("Delete flow classifier failed, "
^
./networking_sfc/services/sfc/driver_manager.py:38:9: N531  Log messages
require translation hints!
LOG.info("Configured SFC drivers: %s", names)
^
./networking_sfc/services/sfc/driver_manager.py:43:9: N531  Log messages
require translation hints!
LOG.info("Loaded SFC drivers: %s", self.names())
^
./networking_sfc/services/sfc/driver_manager.py:78:9: N531  Log messages
require translation hints!
LOG.info("Registered SFC drivers: %s",
^
./networking_sfc/services/sfc/driver_manager.py:85:13: N531  Log messages
require translation hints!
LOG.info("Initializing SFC driver '%s'", driver.name)
^
./networking_sfc/services/sfc/driver_manager.py:104:17: N531  Log messages
require translation hints!
LOG.error(
^
./networking_sfc/services/sfc/plugin.py:57:17: N531  Log messages require
translation hints!
LOG.error("Create port chain failed, "
^
./networking_sfc/services/sfc/plugin.py:82:17: N531  Log messages require
translation hints!
LOG.error("Update port chain failed, port_chain '%s'",
^
./networking_sfc/services/sfc/plugin.py:97:17: N531  Log messages require
translation hints!
LOG.error("Delete port chain failed, portchain '%s'",
^
./networking_sfc/services/sfc/plugin.py:122:17: N531  Log messages require
translation hints!
LOG.error("Create port pair failed, "
^
./networking_sfc/services/sfc/plugin.py:144:17: N531  Log messages require
translation hints!
LOG.error("Update port pair failed, port_pair '%s'",
^
./networking_sfc/services/sfc/plugin.py:159:17: N531  Log messages require
translation hints!
LOG.error("Delete port pair failed, port_pair '%s'",
^
./networking_sfc/services/sfc/plugin.py:185:17: N531  Log messages require
translation hints!
LOG.error("Create port pair group failed, "
^
./networking_sfc/services/sfc/plugin.py:213:17: N531  Log messages require
translation hints!
LOG.error("Update port pair group failed, "
^
./networking_sfc/services/sfc/plugin.py:229:17: N531  Log messages require
translation hints!
LOG.error("Delete port pair group failed, "
^
./networking_sfc/services/sfc/agent/extensions/sfc.py:111:13: N531  Log
messages require translation hints!
LOG.error("SFC L2 extension handle_port failed")
^
./networking_sfc/services/sfc/agent/extensions/sfc.py:124:9: N531  Log
messages require translation hints!
LOG.info("a device %s is removed", port_id)
 

Re: [Openstack] [openstack-dev][openstack] API to get tunnel port connect to other host

[Vikash Kumar]

Hi James,

   I was asking for the tunnel ports on br-tun on every compute.

sudo ovs-vsctl list-ifaces br-tun
patch-int

*vxlan-c0a80265vxlan-c0a802b1*



On Fri, Apr 28, 2017 at 8:41 PM, James Denton <james.den...@rackspace.com>
wrote:

> Hi Vikash,
>
>
>
> The VXLAN tunnel endpoint address is listed in the output of a neutron
> agent-show :
>
>
>
> $ neutron agent-show cb45e3f8-4a28-475a-994d-83bc27806c38
>
> +-++
>
> | Field   | Value  |
>
> +-++
>
> | admin_state_up  | True   |
>
> | agent_type  | Linux bridge agent |
>
> | alive   | True   |
>
> | availability_zone   ||
>
> | binary  | neutron-linuxbridge-agent  |
>
> | configurations  | {  |
>
> | |  "tunneling_ip": "172.29.232.66",  |
>
> | |  "devices": 2, |
>
> | |  "interface_mappings": {   |
>
> | |   "vlan": "br-vlan"|
>
> | |  },|
>
> | |  "extensions": [], |
>
> | |  "l2_population": true,|
>
> | |  "tunnel_types": [ |
>
> | |   "vxlan"  |
>
> | |  ],|
>
> | |  "bridge_mappings": {} |
>
> | | }  |
>
> | created_at  | 2017-04-19 23:12:47|
>
> | description ||
>
> | heartbeat_timestamp | 2017-04-28 15:07:59|
>
> | host| 841445-compute007  |
>
> | id  | cb45e3f8-4a28-475a-994d-83bc27806c38   |
>
> | started_at  | 2017-04-20 17:38:03|
>
> | topic       | N/A|
>
> +-++
>
>
>
> The actual Layer 4 port used may vary between drivers (linuxbridge vs
> OVS), but that would either be hard-coded or defined within a configuration
> file.
>
>
>
> James
>
>
>
> *From: *Vikash Kumar <vikash.ku...@oneconvergence.com>
> *Date: *Friday, April 28, 2017 at 6:50 AM
> *To: *openstack-dev <openstack-...@lists.openstack.org>, Openstack Milis <
> openstack@lists.openstack.org>
> *Subject: *[Openstack] [openstack-dev][openstack] API to get tunnel port
> connect to other host
>
>
>
> Is there any neutron API, which returns the tunnel port details connected
> to other host ?
>
> For eg. I have Host-A and Host-B. Is there a way to know what is the
> tunnel-port on Host-A which connects Host-B ?
>
> Can't use OVS commands directly.
>
>
> --
>
> Regards,
>
> Vikash
>



-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [Openstack] [openstack] API to get tunnel port connect to other host

[Vikash Kumar]

Hi James,

   I was asking for the tunnel ports on br-tun on every compute.

sudo ovs-vsctl list-ifaces br-tun
patch-int

*vxlan-c0a80265vxlan-c0a802b1*



On Fri, Apr 28, 2017 at 8:41 PM, James Denton <james.den...@rackspace.com>
wrote:

> Hi Vikash,
>
>
>
> The VXLAN tunnel endpoint address is listed in the output of a neutron
> agent-show :
>
>
>
> $ neutron agent-show cb45e3f8-4a28-475a-994d-83bc27806c38
>
> +-++
>
> | Field   | Value  |
>
> +-++
>
> | admin_state_up  | True   |
>
> | agent_type  | Linux bridge agent |
>
> | alive   | True   |
>
> | availability_zone   ||
>
> | binary  | neutron-linuxbridge-agent  |
>
> | configurations  | {  |
>
> | |  "tunneling_ip": "172.29.232.66",  |
>
> | |  "devices": 2, |
>
> | |  "interface_mappings": {   |
>
> | |   "vlan": "br-vlan"|
>
> | |  },|
>
> | |  "extensions": [], |
>
> | |  "l2_population": true,|
>
> | |  "tunnel_types": [ |
>
> | |   "vxlan"  |
>
> | |  ],|
>
> | |  "bridge_mappings": {} |
>
> | | }  |
>
> | created_at  | 2017-04-19 23:12:47|
>
> | description ||
>
> | heartbeat_timestamp | 2017-04-28 15:07:59|
>
> | host| 841445-compute007  |
>
> | id  | cb45e3f8-4a28-475a-994d-83bc27806c38   |
>
> | started_at  | 2017-04-20 17:38:03|
>
> | topic       | N/A|
>
> +-++
>
>
>
> The actual Layer 4 port used may vary between drivers (linuxbridge vs
> OVS), but that would either be hard-coded or defined within a configuration
> file.
>
>
>
> James
>
>
>
> *From: *Vikash Kumar <vikash.ku...@oneconvergence.com>
> *Date: *Friday, April 28, 2017 at 6:50 AM
> *To: *openstack-dev <openstack-dev@lists.openstack.org>, Openstack Milis <
> openst...@lists.openstack.org>
> *Subject: *[Openstack] [openstack-dev][openstack] API to get tunnel port
> connect to other host
>
>
>
> Is there any neutron API, which returns the tunnel port details connected
> to other host ?
>
> For eg. I have Host-A and Host-B. Is there a way to know what is the
> tunnel-port on Host-A which connects Host-B ?
>
> Can't use OVS commands directly.
>
>
> --
>
> Regards,
>
> Vikash
>



-- 
Regards,
Vikash
__
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] [openstack-dev][openstack] API to get tunnel port connect to other host

[Vikash Kumar]

Is there any neutron API, which returns the tunnel port details connected
to other host ?

For eg. I have Host-A and Host-B. Is there a way to know what is the
tunnel-port on Host-A which connects Host-B ?

Can't use OVS commands directly.

-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[openstack-dev] [openstack] API to get tunnel port connect to other host

[Vikash Kumar]

Is there any neutron API, which returns the tunnel port details connected
to other host ?

For eg. I have Host-A and Host-B. Is there a way to know what is the
tunnel-port on Host-A which connects Host-B ?

Can't use OVS commands directly.

-- 
Regards,
Vikash
__
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

Re: [openstack-dev] [openstack] How does tag gets allocated to VM ports ?

[Vikash Kumar]

Hi Gary,

   Thanks for pointing the source code. Does this has RFE ? I see for ports
of same network, have different tags on different compute.

On Mon, Apr 3, 2017 at 2:04 PM, Gary Kotton <gkot...@vmware.com> wrote:

> Hi,
>
> This is done by the agents. For example please see
> https://github.com/openstack/neutron/blob/master/neutron/
> plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1639
>
> Thanks
>
> Gary
>
>
>
> *From: *Vikash Kumar <vikash.ku...@oneconvergence.com>
> *Reply-To: *OpenStack List <openstack-dev@lists.openstack.org>
> *Date: *Monday, April 3, 2017 at 9:46 AM
> *To: *OpenStack List <openstack-dev@lists.openstack.org>
> *Subject: *[openstack-dev] [openstack] How does tag gets allocated to VM
> ports ?
>
>
>
> Hi,
>
>How does "tag" gets assigned to openvswitch port ?
> Port "tap319bae97-0b"
> *tag: 1*
> Interface "tap319bae97-0b"
>
> It is done by openvswitch-agent, but can someone point me to the details?
> Is this has anything to do with network (segment-id) or is it just local to
> openvswitch ?
>
>
> --
>
> Regards,
>
> Vikash
>
> __
> 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
>
>


-- 
Regards,
Vikash
__
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-dev] [openstack] How does tag gets allocated to VM ports ?

[Vikash Kumar]

Hi,

   How does "tag" gets assigned to openvswitch port ?
Port "tap319bae97-0b"
*tag: 1*
Interface "tap319bae97-0b"

It is done by openvswitch-agent, but can someone point me to the details?
Is this has anything to do with network (segment-id) or is it just local to
openvswitch ?

-- 
Regards,
Vikash
__
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-dev] [networking-sfc]PPG reuse restriction

[Vikash Kumar]

Hi Team,

  I inserted a single arm SF. Created a port-pair with ingress-port and
egress-port as same. Created rest of the resource and it traffic was as
expected through SF in one direction. After, that I tried to create reverse
flow and it failed due to:

   a. reverse port-chain create failed as ppg in use.
   b. port-pair-create failed as same 'ingress' and 'egress' port is in
use. Thus ppg also can't be created.

So, we can't create a new ppg (with same details) neither can we reuse,
which restrict the reverse path creation by user.

What is the correct solution to achieve same ? What is the implication
if we let the ppg reuse ??

-- 
Regards,
Vikash
__
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

Re: [openstack-dev] [networking-sfc] About insertion modes and SFC Encapsulation

[Vikash Kumar]

Also, for TAP devices, they can be deployed in both active ( forward
traffic back to networking​ devices) and passive mode . Our *current BP*
scope is only for passive TAP. Apart from these two, there are other mode
of deployment s also.

Others reading can add.

On Tue, Mar 21, 2017, 11:16 PM Vikash Kumar <vikash.ku...@oneconvergence.com>
wrote:

Hi Igor,



On Tue, Mar 21, 2017 at 10:02 PM, Duarte Cardoso, Igor <
igor.duarte.card...@intel.com> wrote:

Hi Vikash,



It’s best to start with RFC 7665.



NSH decouples traffic forwarding from both the internals of packets and
service functions. A special entity called SFF will take on that job. L2/L3
then become something that the SFF might have to deal with it.


​which means it can co-exist with (L2/L3 insertion mode) and not
necessarily mutually exclusive.
​


However, networking-sfc API doesn’t expose or require details about
individual SFC dataplane elements such as the SFF… it is up to the
backend/driver to know those low-level details.


​Agree.

​



NSH doesn’t classify and forward traffic itself. It’s only a header that
identifies what and where in the chain the packet belongs to/is (plus other
goodies such as metadata). Classifier will classify, SFF will forward.


​   I was referring to NSH in totality and not excluding SFF (
https://tools.ietf.org/html/draft-ietf-sfc-nsh-12). Look like I extended
the scope of NSH in term of  SFC. ​






By the way, I left a question on the tap blueprint whiteboard, I’ll copy it
here too:

“Is there a use case for "tap chains"? I.e. not only you send traffic to
your tap function, but then your tap function also sends traffic to a next
hop too, so a full chain starts after traffic gets tapped at the first
chain (the first chain also continues).”

I suppose the answer is no since you mentioned “Note - TAP SFs do not
forward packet”, but I’m happy to hear extended info about this – from
anyone reading.



Best regards,

Igor.



*From:* Vikash Kumar [mailto:vikash.ku...@oneconvergence.com]
*Sent:* Tuesday, March 21, 2017 3:32 PM
*To:* OpenStack Development Mailing List (not for usage questions) <
openstack-dev@lists.openstack.org>
*Subject:* Re: [openstack-dev] [networking-sfc] About insertion modes and
SFC Encapsulation



Hi,

   Moving definition of SF from port-pair to port-pair-group looks good.

   TAP is also an insertion mode like L2/L3 but since it simplifies to keep
'tap-enabled' field also in port-pair-group, so it should be fine from
implementation point of view (Note - TAP SFs do not forward packet). TAP
enabled and L2/L3 insertion mode should be mutually exclusive.

   According to IETF draft NSH can classify & forward traffic (correct ?)
but then the draft assumes uniformity of working of devices (which IMHO
refers L3) which doesn't cover the entire use case. Can insertion mode
(L2/L3) & traffic encapsulation(NSH) co-exist also ?






On Mon, Mar 20, 2017 at 11:35 PM, Cathy Zhang <cathy.h.zh...@huawei.com>
wrote:

Hi Igor,



Moving the correlation from port-pair to port-pair-group makes sense. In
the future I think we should add all new attributes for a SF to
port-pair-group-param.



But I think L2/L3 is different from encap type NSH or MPLS. An L3 type SF
can support either NSH or MPLS. I would suggest the following:



port-pair-group (port-pair-group-params):

insertion-mode:

- L2

- L3 (default)

   Correlation:

- MPLS

- NSH

tap-enabled:

- False (default)

- True



Thanks,

Cathy



*From:* Duarte Cardoso, Igor [mailto:igor.duarte.card...@intel.com]
*Sent:* Monday, March 20, 2017 8:02 AM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* [openstack-dev] [networking-sfc] About insertion modes and SFC
Encapsulation



Hi networking-sfc,



At the latest IRC meeting [1] it was agreed to split TAP from the possible
insertion modes (initial spec version [2]).



I took the ARs to propose coexistence of insertion modes, correlation and
(now) a new tap-enabled attribute, and send this email about possible
directions.



Here are my thoughts, let me know yours:



1.   My expectation for future PP and PPG if TAP+insertion modes go
ahead and nothing else changes (only relevant details outlined):



port-pair (service-function-params):

correlation:

- MPLS

- None (default)

port-pair-group (port-pair-group-params):

insertion-mode:

- L2

- L3 (default)

tap-enabled:

- False (default)

- True



2.   What I propose for future PP and PPG (only relevan

Re: [openstack-dev] [networking-sfc] About insertion modes and SFC Encapsulation

[Vikash Kumar]

Hi,

   Moving definition of SF from port-pair to port-pair-group looks good.

   TAP is also an insertion mode like L2/L3 but since it simplifies to keep
'tap-enabled' field also in port-pair-group, so it should be fine from
implementation point of view (Note - TAP SFs do not forward packet). TAP
enabled and L2/L3 insertion mode should be mutually exclusive.

   According to IETF draft NSH can classify & forward traffic (correct ?)
but then the draft assumes uniformity of working of devices (which IMHO
refers L3) which doesn't cover the entire use case. Can insertion mode
(L2/L3) & traffic encapsulation(NSH) co-exist also ?



On Mon, Mar 20, 2017 at 11:35 PM, Cathy Zhang 
wrote:

> Hi Igor,
>
>
>
> Moving the correlation from port-pair to port-pair-group makes sense. In
> the future I think we should add all new attributes for a SF to
> port-pair-group-param.
>
>
>
> But I think L2/L3 is different from encap type NSH or MPLS. An L3 type SF
> can support either NSH or MPLS. I would suggest the following:
>
>
>
> port-pair-group (port-pair-group-params):
>
> insertion-mode:
>
> - L2
>
> - L3 (default)
>
>Correlation:
>
> - MPLS
>
> - NSH
>
> tap-enabled:
>
> - False (default)
>
> - True
>
>
>
> Thanks,
>
> Cathy
>
>
>
> *From:* Duarte Cardoso, Igor [mailto:igor.duarte.card...@intel.com]
> *Sent:* Monday, March 20, 2017 8:02 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* [openstack-dev] [networking-sfc] About insertion modes and SFC
> Encapsulation
>
>
>
> Hi networking-sfc,
>
>
>
> At the latest IRC meeting [1] it was agreed to split TAP from the possible
> insertion modes (initial spec version [2]).
>
>
>
> I took the ARs to propose coexistence of insertion modes, correlation and
> (now) a new tap-enabled attribute, and send this email about possible
> directions.
>
>
>
> Here are my thoughts, let me know yours:
>
>
>
> 1.   My expectation for future PP and PPG if TAP+insertion modes go
> ahead and nothing else changes (only relevant details outlined):
>
>
>
> port-pair (service-function-params):
>
> correlation:
>
> - MPLS
>
> - None (default)
>
> port-pair-group (port-pair-group-params):
>
> insertion-mode:
>
> - L2
>
> - L3 (default)
>
> tap-enabled:
>
> - False (default)
>
> - True
>
>
>
> 2.   What I propose for future PP and PPG (only relevant details
> outlined):
>
>
>
> port-pair (service-function-params):
>
> 
>
> port-pair-group (port-pair-group-params):
>
> mode:
>
> - L2
>
> - L3 (default)
>
> - MPLS
>
> - NSH
>
> tap-enabled:
>
> - False (default)
>
> - True
>
>
>
> With what’s proposed in 2.:
>
> - every combination will be possible with no clashes and no validation
> required.
>
> - port-pair-groups will always group “homogeneous” sets of port-pairs,
> making load-balacing and next-hop processing simpler and consistent.
>
> - the “forwarding” details of a Service Function are no longer dictated
> both by port-pair and port-pair-group, but rather only by port-pair-group.
>
>
>
> Are there any use cases for having next-hop SF candidates (individual
> port-pairs) supporting different SFC Encapsulation protocols?
>
> I understand, however, that removing correlation from port-pairs might not
> be ideal given that it’s a subtractive API change.
>
>
>
> [1] http://eavesdrop.openstack.org/meetings/service_chaining/201
> 7/service_chaining.2017-03-16-17.02.html
>
> [2] https://review.openstack.org/#/c/442195/
>
> [3] https://github.com/openstack/networking-sfc/blob/17c537b35d4
> 1a3e1fd80da790ae668e52cea6b88/doc/source/system_design%
> 20and_workflow.rst#usage
>
>
>
> Best regards,
>
> Igor.
>
> __
> 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
>
>


-- 
Regards,
Vikash
__
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

Re: [Openstack] [nova][nova-scheduler]There are 0 host available

[Vikash Kumar]

I had this compute node which nova service-list was showing.

*nfp  nova*# Compute node

On Tue, Mar 14, 2017 at 10:42 PM, Hauke Bruno Wollentin <
hauke-bruno.wollen...@innovo-cloud.de> wrote:

> Hi Vikash,
>
> Did you make sure that your compute node is running?
>
> 'nova availability-zone-list' (or the equivalent openstack cli command)
> will show you that.
>
> If your compute node isn't active, you need to check whether
> nova-compute throws errors on your compute node.
>
> cheers,
> hauke
>
> On 14.03.2017 06:22, Vikash Kumar wrote:
> > I am unable to launch the instance. Below is Nova scheduler logs which
> > says 0 host. I have installed openstack ocata devstack. Here is output
> of :
> >
> > *nova-manage host list
> > host zone
> > 0.0.0.0  internal
> > stackinternal
> > nfp  nova*# Compute node
> >
> > 2017-03-14 10:13:15.949 24225 DEBUG oslo_service.periodic_task
> > [req-b6c01e64-17e9-4f57-aec8-4bf7ba279e8f - -] Running periodic task
> > SchedulerManager._
> > run_periodic_tasks run_periodic_tasks
> > /usr/local/lib/python2.7/dist-packages/oslo_service/periodic_task.py:215
> > 2017-03-14 10:13:52.178 24225 DEBUG oslo_messaging._drivers.amqpdriver
> > [-] received message with unique_id: 3b9519dd6abb4a808433f594dda3c8ba
> > __call__
> > /usr/local/lib/python2.7/dist-packages/oslo_messaging/_
> drivers/amqpdriver.py:196
> > 2017-03-14 10:13:52.180 24225 DEBUG oslo_concurrency.lockutils
> > [req-fafcd5e5-0278-447e-ace4-a67defd17816 - -] Lock "host_instance"
> > acquired by "nova.s
> > cheduler.host_manager.update_instance_info" :: waited 0.000s inner
> > /usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:270
> > 2017-03-14 10:13:52.181 24225 DEBUG oslo_concurrency.lockutils
> > [req-fafcd5e5-0278-447e-ace4-a67defd17816 - -] Lock "host_instance"
> > released by "nova.s
> > cheduler.host_manager.update_instance_info" :: held 0.001s inner
> > /usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:282
> > 2017-03-14 10:14:04.230 24225 DEBUG oslo_service.periodic_task
> > [req-b6c01e64-17e9-4f57-aec8-4bf7ba279e8f - -] Running periodic task
> > SchedulerManager._
> > expire_reservations run_periodic_tasks
> > /usr/local/lib/python2.7/dist-packages/oslo_service/periodic_task.py:215
> > 2017-03-14 10:14:15.951 24225 DEBUG oslo_service.periodic_task
> > [req-b6c01e64-17e9-4f57-aec8-4bf7ba279e8f - -] Running periodic task
> > SchedulerManager._
> > run_periodic_tasks run_periodic_tasks
> > /usr/local/lib/python2.7/dist-packages/oslo_service/periodic_task.py:215
> > 2017-03-14 10:14:34.614 24225 DEBUG oslo_messaging._drivers.amqpdriver
> > [-] received message msg_id: 7bd0be86818e42a58d845a4e783efbd4 reply to
> > reply_49
> > 01cb308942488984a83a9e2275f6b5 __call__
> > /usr/local/lib/python2.7/dist-packages/oslo_messaging/_
> drivers/amqpdriver.py:194
> > 2017-03-14 10:14:34.617 24225 DEBUG oslo_messaging._drivers.amqpdriver
> > [req-babb1ec2-2619-4d9b-8677-33e928b6e66f vks vks] CAST unique_id:
> > b118ce0d7da0
> > 43b2bfee3c63f5939ff4 NOTIFY exchange 'nova' topic 'notifications.info
> > <http://notifications.info>' _send
> > /usr/local/lib/python2.7/dist-packages/oslo_messaging/_
> drivers/amqpdriver.py:426
> > 2017-03-14 10:14:44.112 24225 DEBUG nova.filters
> > [req-babb1ec2-2619-4d9b-8677-33e928b6e66f vks vks] *Starting with 0
> > host(s) get_filtered_objects /opt/stack/nova/nova/filters.py:70*
> > 2017-03-14 10:14:44.113 24225 INFO nova.filters
> > [req-babb1ec2-2619-4d9b-8677-33e928b6e66f vks vks] Filter RetryFilter
> > returned 0 hosts
> > 2017-03-14 10:14:44.114 24225 DEBUG nova.filters
> > [req-babb1ec2-2619-4d9b-8677-33e928b6e66f vks vks] Filtering removed all
> > hosts for the request with instance ID
> > 'ebce31a7-7018-4f2e-980c-e10987afdca6'. Filter results: [('RetryFilter',
> > None)] get_filtered_objects /opt/stack/nova/nova/filters.py:129
> > 2017-03-14 10:14:44.115 24225 INFO nova.filters
> > [req-babb1ec2-2619-4d9b-8677-33e928b6e66f vks vks] Filtering removed all
> > hosts for the request with instance ID
> > 'ebce31a7-7018-4f2e-980c-e10987afdca6'. Filter results: ['RetryFilter:
> > (start: 0, end: 0)']
> > 2017-03-14 10:14:44.116 24225 DEBUG nova.scheduler.filter_scheduler
> > [req-babb1ec2-2619-4d9b-8677-33e928b6e66f vks vks] T*here are 0 hosts
> > available but 1 instances requested to build. select_destinations
> > 

Re: [openstack-dev] 回复： [nova][nova-scheduler] Instance boot stuck in"Scheduling" state

[Vikash Kumar]

Thanks Prashant,

I have chkd that. Does it have anything to run controller and compute
on single node as solution ?

On Tue, Mar 14, 2017 at 8:52 PM, Prashant Shetty <
prashantshetty1...@gmail.com> wrote:

> Couple of things to check,
>
>- On controller in nova.conf you should have [placement] section with
>below info
>   - [placement]
>   os_region_name = RegionOne
>   project_domain_name = Default
>   project_name = service
>   user_domain_name = Default
>   password = 
>   username = placement
>   auth_url = 
>   auth_type = password
>- If nova service-list shows your nova-compute is UP and RUNNING, you
>need to run discover commands on controller as below
>   - nova-manage cell_v2 map_cell0 --database_connection 
>   - nova-manage cell_v2 simple_cell_setup --transport-url
>   
>   - nova-manage cell_v2 discover_hosts --verbose
>
> Discover command should show message that it has discovered your compute
> nodes. In case still instance launch fails check nova-conductor and
> nova-scheduler logs for more info.
>
> For more information refer, https://docs.openstack.org/
> developer/nova/cells.html
>
>
> Thanks,
>
> Prashant
>
> On Tue, Mar 14, 2017 at 8:33 PM, Vikash Kumar <
> vikash.ku...@oneconvergence.com> wrote:
>
>> That was the weird thing. nova-compute doesn't had any error log.
>> nova-compute logs also didn't had any instance create request also.
>>
>> On Tue, Mar 14, 2017 at 7:50 PM, luogangyi@chinamobile <
>> luogan...@chinamobile.com> wrote:
>>
>>> From your log, we can see nova scheduler has already select target node
>>> which is u’nfp’.
>>>
>>>
>>> So you should check the nova-compute log from node nfp.
>>>
>>>
>>> Probably, you are stuck at image downloading.
>>>
>>>  原始邮件
>>> *发件人:* Vikash Kumar<vikash.ku...@oneconvergence.com>
>>> *收件人:* openstack-dev<openstack-dev@lists.openstack.org>
>>> *发送时间:* 2017年3月14日(周二) 18:22
>>> *主题:* [openstack-dev] [nova][nova-scheduler] Instance boot stuck
>>> in"Scheduling" state
>>>
>>> All,
>>>
>>> I brought up multinode setup with devstack. I am using Ocata
>>> release. Instances boot are getting stuck in "scheduling" state. The state
>>> never gets changed. Below is the link for scheduler log.
>>>
>>> http://paste.openstack.org/show/602635/
>>>
>>>
>>> --
>>> Regards,
>>> Vikash
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>> Regards,
>> Vikash
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> 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
>
>


-- 
Regards,
Vikash
__
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

Re: [openstack-dev] 回复： [nova][nova-scheduler] Instance boot stuck in"Scheduling" state

[Vikash Kumar]

That was the weird thing. nova-compute doesn't had any error log.
nova-compute logs also didn't had any instance create request also.

On Tue, Mar 14, 2017 at 7:50 PM, luogangyi@chinamobile <
luogan...@chinamobile.com> wrote:

> From your log, we can see nova scheduler has already select target node
> which is u’nfp’.
>
>
> So you should check the nova-compute log from node nfp.
>
>
> Probably, you are stuck at image downloading.
>
>  原始邮件
> *发件人:* Vikash Kumar<vikash.ku...@oneconvergence.com>
> *收件人:* openstack-dev<openstack-dev@lists.openstack.org>
> *发送时间:* 2017年3月14日(周二) 18:22
> *主题:* [openstack-dev] [nova][nova-scheduler] Instance boot stuck
> in"Scheduling" state
>
> All,
>
> I brought up multinode setup with devstack. I am using Ocata release.
> Instances boot are getting stuck in "scheduling" state. The state never
> gets changed. Below is the link for scheduler log.
>
> http://paste.openstack.org/show/602635/
>
>
> --
> Regards,
> Vikash
>
> __
> 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
>
>


-- 
Regards,
Vikash
__
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-dev] [nova][nova-scheduler] Instance boot stuck in "Scheduling" state

[Vikash Kumar]

All,

I brought up multinode setup with devstack. I am using Ocata release.
Instances boot are getting stuck in "scheduling" state. The state never
gets changed. Below is the link for scheduler log.

http://paste.openstack.org/show/602635/


-- 
Regards,
Vikash
__
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] [nova][nova-scheduler]There are 0 host available

[Vikash Kumar]

I am unable to launch the instance. Below is Nova scheduler logs which says
0 host. I have installed openstack ocata devstack. Here is output of :





*nova-manage host listhost zone
0.0.0.0  internal   stack
internal   nfp  nova*# Compute node

2017-03-14 10:13:15.949 24225 DEBUG oslo_service.periodic_task
[req-b6c01e64-17e9-4f57-aec8-4bf7ba279e8f - -] Running periodic task
SchedulerManager._
run_periodic_tasks run_periodic_tasks
/usr/local/lib/python2.7/dist-packages/oslo_service/periodic_task.py:215
2017-03-14 10:13:52.178 24225 DEBUG oslo_messaging._drivers.amqpdriver [-]
received message with unique_id: 3b9519dd6abb4a808433f594dda3c8ba __call__
/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:196
2017-03-14 10:13:52.180 24225 DEBUG oslo_concurrency.lockutils
[req-fafcd5e5-0278-447e-ace4-a67defd17816 - -] Lock "host_instance"
acquired by "nova.s
cheduler.host_manager.update_instance_info" :: waited 0.000s inner
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:270
2017-03-14 10:13:52.181 24225 DEBUG oslo_concurrency.lockutils
[req-fafcd5e5-0278-447e-ace4-a67defd17816 - -] Lock "host_instance"
released by "nova.s
cheduler.host_manager.update_instance_info" :: held 0.001s inner
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:282
2017-03-14 10:14:04.230 24225 DEBUG oslo_service.periodic_task
[req-b6c01e64-17e9-4f57-aec8-4bf7ba279e8f - -] Running periodic task
SchedulerManager._
expire_reservations run_periodic_tasks
/usr/local/lib/python2.7/dist-packages/oslo_service/periodic_task.py:215
2017-03-14 10:14:15.951 24225 DEBUG oslo_service.periodic_task
[req-b6c01e64-17e9-4f57-aec8-4bf7ba279e8f - -] Running periodic task
SchedulerManager._
run_periodic_tasks run_periodic_tasks
/usr/local/lib/python2.7/dist-packages/oslo_service/periodic_task.py:215
2017-03-14 10:14:34.614 24225 DEBUG oslo_messaging._drivers.amqpdriver [-]
received message msg_id: 7bd0be86818e42a58d845a4e783efbd4 reply to reply_49
01cb308942488984a83a9e2275f6b5 __call__
/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:194
2017-03-14 10:14:34.617 24225 DEBUG oslo_messaging._drivers.amqpdriver
[req-babb1ec2-2619-4d9b-8677-33e928b6e66f vks vks] CAST unique_id:
b118ce0d7da0
43b2bfee3c63f5939ff4 NOTIFY exchange 'nova' topic 'notifications.info'
_send
/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:426
2017-03-14 10:14:44.112 24225 DEBUG nova.filters
[req-babb1ec2-2619-4d9b-8677-33e928b6e66f vks vks] *Starting with 0 host(s)
get_filtered_objects /opt/stack/nova/nova/filters.py:70*
2017-03-14 10:14:44.113 24225 INFO nova.filters
[req-babb1ec2-2619-4d9b-8677-33e928b6e66f vks vks] Filter RetryFilter
returned 0 hosts
2017-03-14 10:14:44.114 24225 DEBUG nova.filters
[req-babb1ec2-2619-4d9b-8677-33e928b6e66f vks vks] Filtering removed all
hosts for the request with instance ID
'ebce31a7-7018-4f2e-980c-e10987afdca6'. Filter results: [('RetryFilter',
None)] get_filtered_objects /opt/stack/nova/nova/filters.py:129
2017-03-14 10:14:44.115 24225 INFO nova.filters
[req-babb1ec2-2619-4d9b-8677-33e928b6e66f vks vks] Filtering removed all
hosts for the request with instance ID
'ebce31a7-7018-4f2e-980c-e10987afdca6'. Filter results: ['RetryFilter:
(start: 0, end: 0)']
2017-03-14 10:14:44.116 24225 DEBUG nova.scheduler.filter_scheduler
[req-babb1ec2-2619-4d9b-8677-33e928b6e66f vks vks] T*here are 0 hosts
available but 1 instances requested to build. select_destinations
/opt/stack/nova/nova/scheduler/filter_scheduler.py:76*
2017-03-14 10:14:44.117 24225 DEBUG oslo_messaging.rpc.server
[req-babb1ec2-2619-4d9b-8677-33e928b6e66f vks vks] Expected exception
during message handling () _process_incoming
/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py:158
2017-03-14 10:14:44.118 24225 DEBUG oslo_messaging._drivers.amqpdriver
[req-babb1ec2-2619-4d9b-8677-33e928b6e66f vks vks] sending reply msg_id:
7bd0be86818e42a58d845a4e783efbd4 reply queue:
reply_4901cb308942488984a83a9e2275f6b5 time elapsed: 9.50398825854s
_send_reply
/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:73

Is this a filter isssue ?





-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [networking-sfc] patch test failed due to "import error: vlanmanager"

[Vikash Kumar]

Hi Igor,

I was trying on Ubuntu 14.04 (trusty). This was weird though.

On Thu, Mar 9, 2017 at 4:54 PM, Duarte Cardoso, Igor <
igor.duarte.card...@intel.com> wrote:

> Hi Vikash,
>
>
>
> What OS were you trying on before?
>
>
>
> Best regards,
>
> Igor.
>
>
>
> *From:* Vikash Kumar [mailto:vikash.ku...@oneconvergence.com]
> *Sent:* Thursday, March 9, 2017 10:08 AM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>; ke...@benton.pub
>
> *Subject:* Re: [openstack-dev] [networking-sfc] patch test failed due to
> "import error: vlanmanager"
>
>
>
> Tried on Ubuntu 16.04, its fine.
>
>
>
> On Thu, Mar 9, 2017 at 12:17 PM, Vikash Kumar <
> vikash.ku...@oneconvergence.com> wrote:
>
> Import path looks OK
> https://github.com/openstack/networking-sfc/blob/master/
> networking_sfc/services/sfc/agent/extensions/openvswitch/sfc_driver.py#L23
>
>
>
> Are u suggesting something else?
>
>
>
> On Thu, Mar 9, 2017 at 3:02 AM, Kevin Benton <ke...@benton.pub> wrote:
>
> That location was recently changed in the Neutron side.[1] It sounds like
> sfc has to be updated.
>
>
>
> 1. https://github.com/openstack/neutron/commit/
> 4ec456d31501f09c68b5c23c488878da32dce75e
>
>
>
> On Tue, Mar 7, 2017 at 9:41 PM, Vikash Kumar <vikash.kumar@oneconvergence.
> com> wrote:
>
> Hi Igor,
>
>This is weird. I just did a fresh clone and executed *"tox" *command.
> I am getting same error. Am I missing anything here ? There is no private
> change here.  Below is the link for entire log.
>
>  http://paste.openstack.org/show/601870/
>
>
>
> On Tue, Mar 7, 2017 at 10:46 PM, Duarte Cardoso, Igor <
> igor.duarte.card...@intel.com> wrote:
>
> Hi Vikash,
>
> Please stick to pastebin for complete logs.
>
>
>
> Check your migration files:
>
>
>
> FAILED: Contract HEAD file does not match migration timeline head,
> expected: 48072cb59133
>
>
>
> Best regards,
>
> Igor.
>
>
>
> *From:* Vikash Kumar [mailto:vikash.ku...@oneconvergence.com]
> *Sent:* Tuesday, March 7, 2017 5:03 PM
> *To:* openstack-dev <openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [networking-sfc] patch test failed due to
> "import error: vlanmanager"
>
>
>
> Complete log:
>
>  py35 create: /home/vikash/guess_vk/python-dev/networking-sfc/.tox/py35
> py35 installdeps: 
> -r/home/vikash/guess_vk/python-dev/networking-sfc/requirements.txt,
> -r/home/vikash/guess_vk/python-dev/networking-sfc/test-requirements.txt
> py35 develop-inst: /home/vikash/guess_vk/python-dev/networking-sfc
> py35 installed: 
> /home/vikash/guess_vk/python-dev/networking-sfc/.tox/py35/lib/python3.5/site.py:165:
> DeprecationWarning: 'U' mode is deprecated,  f = open(fullname,
> "rU"),alabaster==0.7.10,alembic==0.9.1,amqp==1.4.9,
> anyjson==0.3.3,appdirs==1.4.2,astroid==1.3.8,Babel==2.3.4,
> beautifulsoup4==4.5.3,cachetools==2.0.0,cffi==1.9.1,
> cliff==2.4.0,cmd2==0.7.0,contextlib2==0.5.4,coverage==
> 4.3.4,cryptography==1.7.2,debtcollector==1.12.0,
> decorator==4.0.11,docutils==0.13.1,dulwich==0.17.1,eventlet=
> =0.19.0,extras==1.0.0,fasteners==0.14.1,fixtures==3.
> 0.0,flake8==2.5.5,futurist==0.21.0,greenlet==0.4.12,hacking=
> =0.12.0,httplib2==0.10.3,idna==2.4,imagesize==0.7.1,iso8601=
> =0.1.11,Jinja2==2.9.5,jsonpatch==1.15,jsonpointer==1.10,jsonschema==2.6.0,
> keystoneauth1==2.18.0,keystonemiddleware==4.14.0,
> kombu==3.0.37,linecache2==1.0.0,logilab-common==1.3.0,
> logutils==0.3.4.1,Mako==1.0.6,MarkupSafe==0.23,mccabe==0.2.
> 1,mock==2.0.0,monotonic==1.2,mox3==0.20.0,msgpack-python==
> 0.4.8,netaddr==0.7.19,netifaces==0.10.5,-e git+https://github.com/
> openstack/networking-sfc.git@c51052e3748e917731f449b0ff4dc2
> 0d2e484490#egg=networking_sfc,-e git+https://github.com/
> openstack/neutron.git@41be555eddb0f9947fdaa4e73fa74a
> 72677d4d11#egg=neutron,neutron-lib==1.2.0,openstackdocstheme==1.6.1,
> openstacksdk==0.9.13,os-api-ref==1.3.0,os-client-config==
> 1.26.0,os-testr==0.8.0,osc-lib==1.3.0,oslo.concurrency==
> 3.19.0,oslo.config==3.22.0,oslo.context==2.12.1,oslo.db==
> 4.17.0,oslo.i18n==3.13.0,oslo.log==3.21.0,oslo.messaging==5.
> 18.0,oslo.middleware==3.23.1,oslo.policy==1.19.0,oslo.
> reports==1.17.0,oslo.rootwrap==5.4.0,oslo.serialization==2.
> 17.0,oslo.service==1.19.0,oslo.utils==3.22.0,oslo.
> versionedobjects==1.22.0,oslosphinx==4.10.0,oslotest==
> 2.14.0,ovs==2.7.0,packaging==16.8,paramiko==2.1.2,Paste==2.
> 0.3,PasteDeploy==1.5.2,pbr==2.0.0,pecan==1.2.1,pep8==1.5.7,
> pika==0.10.0,pika-pool==0.1.3,positional==1.1.1,prett

Re: [openstack-dev] [networking-sfc] patch test failed due to "import error: vlanmanager"

[Vikash Kumar]

Tried on Ubuntu 16.04, its fine.

On Thu, Mar 9, 2017 at 12:17 PM, Vikash Kumar <
vikash.ku...@oneconvergence.com> wrote:

> Import path looks OK
> https://github.com/openstack/networking-sfc/blob/master/
> networking_sfc/services/sfc/agent/extensions/openvswitch/sfc_driver.py#L23
>
>
> Are u suggesting something else?
>
> On Thu, Mar 9, 2017 at 3:02 AM, Kevin Benton <ke...@benton.pub> wrote:
>
>> That location was recently changed in the Neutron side.[1] It sounds like
>> sfc has to be updated.
>>
>> 1. https://github.com/openstack/neutron/commit/4ec456d31501f
>> 09c68b5c23c488878da32dce75e
>>
>> On Tue, Mar 7, 2017 at 9:41 PM, Vikash Kumar <
>> vikash.ku...@oneconvergence.com> wrote:
>>
>>> Hi Igor,
>>>
>>>This is weird. I just did a fresh clone and executed *"tox" *command.
>>> I am getting same error. Am I missing anything here ? There is no private
>>> change here.  Below is the link for entire log.
>>>
>>>  http://paste.openstack.org/show/601870/
>>>
>>> On Tue, Mar 7, 2017 at 10:46 PM, Duarte Cardoso, Igor <
>>> igor.duarte.card...@intel.com> wrote:
>>>
>>>> Hi Vikash,
>>>>
>>>> Please stick to pastebin for complete logs.
>>>>
>>>>
>>>>
>>>> Check your migration files:
>>>>
>>>>
>>>>
>>>> FAILED: Contract HEAD file does not match migration timeline head,
>>>> expected: 48072cb59133
>>>>
>>>>
>>>>
>>>> Best regards,
>>>>
>>>> Igor.
>>>>
>>>>
>>>>
>>>> *From:* Vikash Kumar [mailto:vikash.ku...@oneconvergence.com]
>>>> *Sent:* Tuesday, March 7, 2017 5:03 PM
>>>> *To:* openstack-dev <openstack-dev@lists.openstack.org>
>>>> *Subject:* Re: [openstack-dev] [networking-sfc] patch test failed due
>>>> to "import error: vlanmanager"
>>>>
>>>>
>>>>
>>>> Complete log:
>>>>
>>>>  py35 create: /home/vikash/guess_vk/python-dev/networking-sfc/.tox/py35
>>>> py35 installdeps: -r/home/vikash/guess_vk/python
>>>> -dev/networking-sfc/requirements.txt, -r/home/vikash/guess_vk/python
>>>> -dev/networking-sfc/test-requirements.txt
>>>> py35 develop-inst: /home/vikash/guess_vk/python-dev/networking-sfc
>>>> py35 installed: /home/vikash/guess_vk/python-d
>>>> ev/networking-sfc/.tox/py35/lib/python3.5/site.py:165:
>>>> DeprecationWarning: 'U' mode is deprecated,  f = open(fullname,
>>>> "rU"),alabaster==0.7.10,alembic==0.9.1,amqp==1.4.9,anyjson==
>>>> 0.3.3,appdirs==1.4.2,astroid==1.3.8,Babel==2.3.4,beautifulso
>>>> up4==4.5.3,cachetools==2.0.0,cffi==1.9.1,cliff==2.4.0,cmd2==
>>>> 0.7.0,contextlib2==0.5.4,coverage==4.3.4,cryptography==1.7.2
>>>> ,debtcollector==1.12.0,decorator==4.0.11,docutils==0.13.1,du
>>>> lwich==0.17.1,eventlet==0.19.0,extras==1.0.0,fasteners==0.
>>>> 14.1,fixtures==3.0.0,flake8==2.5.5,futurist==0.21.0,greenle
>>>> t==0.4.12,hacking==0.12.0,httplib2==0.10.3,idna==2.4,ima
>>>> gesize==0.7.1,iso8601==0.1.11,Jinja2==2.9.5,jsonpatch==1.15,
>>>> jsonpointer==1.10,jsonschema==2.6.0,keystoneauth1==2.18.0,
>>>> keystonemiddleware==4.14.0,kombu==3.0.37,linecache2==1.0.0,
>>>> logilab-common==1.3.0,logutils==0.3.4.1,Mako==1.0.6,MarkupSa
>>>> fe==0.23,mccabe==0.2.1,mock==2.0.0,monotonic==1.2,mox3==0.
>>>> 20.0,msgpack-python==0.4.8,netaddr==0.7.19,netifaces==0.10.5,-e git+
>>>> https://github.com/openstack/networking-sfc.git@c51052e3
>>>> 748e917731f449b0ff4dc20d2e484490#egg=networking_sfc,-e git+
>>>> https://github.com/openstack/neutron.git@41be555eddb0f99
>>>> 47fdaa4e73fa74a72677d4d11#egg=neutron,neutron-lib==1.2.0,ope
>>>> nstackdocstheme==1.6.1,openstacksdk==0.9.13,os-api-ref==1.3.
>>>> 0,os-client-config==1.26.0,os-testr==0.8.0,osc-lib==1.3.0,os
>>>> lo.concurrency==3.19.0,oslo.config==3.22.0,oslo.context==2.1
>>>> 2.1,oslo.db==4.17.0,oslo.i18n==3.13.0,oslo.log==3.21.0,oslo.
>>>> messaging==5.18.0,oslo.middleware==3.23.1,oslo.policy==1.19.
>>>> 0,oslo.reports==1.17.0,oslo.rootwrap==5.4.0,oslo.serializa
>>>> tion==2.17.0,oslo.service==1.19.0,oslo.utils==3.22.0,oslo.
>>>> versionedobjects==1.22.0,oslosphinx==4.10.0,oslotest==
>>>> 2.14.0,ovs==2.7.0,packaging==16.8,paramiko==2.1.2,Paste==2

Re: [openstack-dev] [networking-sfc] patch test failed due to "import error: vlanmanager"

[Vikash Kumar]

Import path looks OK
https://github.com/openstack/networking-sfc/blob/master/networking_sfc/services/sfc/agent/extensions/openvswitch/sfc_driver.py#L23


Are u suggesting something else?

On Thu, Mar 9, 2017 at 3:02 AM, Kevin Benton <ke...@benton.pub> wrote:

> That location was recently changed in the Neutron side.[1] It sounds like
> sfc has to be updated.
>
> 1. https://github.com/openstack/neutron/commit/
> 4ec456d31501f09c68b5c23c488878da32dce75e
>
> On Tue, Mar 7, 2017 at 9:41 PM, Vikash Kumar <vikash.kumar@oneconvergence.
> com> wrote:
>
>> Hi Igor,
>>
>>This is weird. I just did a fresh clone and executed *"tox" *command.
>> I am getting same error. Am I missing anything here ? There is no private
>> change here.  Below is the link for entire log.
>>
>>  http://paste.openstack.org/show/601870/
>>
>> On Tue, Mar 7, 2017 at 10:46 PM, Duarte Cardoso, Igor <
>> igor.duarte.card...@intel.com> wrote:
>>
>>> Hi Vikash,
>>>
>>> Please stick to pastebin for complete logs.
>>>
>>>
>>>
>>> Check your migration files:
>>>
>>>
>>>
>>> FAILED: Contract HEAD file does not match migration timeline head,
>>> expected: 48072cb59133
>>>
>>>
>>>
>>> Best regards,
>>>
>>> Igor.
>>>
>>>
>>>
>>> *From:* Vikash Kumar [mailto:vikash.ku...@oneconvergence.com]
>>> *Sent:* Tuesday, March 7, 2017 5:03 PM
>>> *To:* openstack-dev <openstack-dev@lists.openstack.org>
>>> *Subject:* Re: [openstack-dev] [networking-sfc] patch test failed due
>>> to "import error: vlanmanager"
>>>
>>>
>>>
>>> Complete log:
>>>
>>>  py35 create: /home/vikash/guess_vk/python-dev/networking-sfc/.tox/py35
>>> py35 installdeps: -r/home/vikash/guess_vk/python
>>> -dev/networking-sfc/requirements.txt, -r/home/vikash/guess_vk/python
>>> -dev/networking-sfc/test-requirements.txt
>>> py35 develop-inst: /home/vikash/guess_vk/python-dev/networking-sfc
>>> py35 installed: /home/vikash/guess_vk/python-d
>>> ev/networking-sfc/.tox/py35/lib/python3.5/site.py:165:
>>> DeprecationWarning: 'U' mode is deprecated,  f = open(fullname,
>>> "rU"),alabaster==0.7.10,alembic==0.9.1,amqp==1.4.9,anyjson==
>>> 0.3.3,appdirs==1.4.2,astroid==1.3.8,Babel==2.3.4,beautifulso
>>> up4==4.5.3,cachetools==2.0.0,cffi==1.9.1,cliff==2.4.0,cmd2==
>>> 0.7.0,contextlib2==0.5.4,coverage==4.3.4,cryptography==1.7.
>>> 2,debtcollector==1.12.0,decorator==4.0.11,docutils==0.13.1,
>>> dulwich==0.17.1,eventlet==0.19.0,extras==1.0.0,fasteners==
>>> 0.14.1,fixtures==3.0.0,flake8==2.5.5,futurist==0.21.0,
>>> greenlet==0.4.12,hacking==0.12.0,httplib2==0.10.3,idna==2.4,
>>> imagesize==0.7.1,iso8601==0.1.11,Jinja2==2.9.5,jsonpatch==1.
>>> 15,jsonpointer==1.10,jsonschema==2.6.0,keystoneauth1==2.18.
>>> 0,keystonemiddleware==4.14.0,kombu==3.0.37,linecache2==1.0.
>>> 0,logilab-common==1.3.0,logutils==0.3.4.1,Mako==1.0.6,
>>> MarkupSafe==0.23,mccabe==0.2.1,mock==2.0.0,monotonic==1.2,
>>> mox3==0.20.0,msgpack-python==0.4.8,netaddr==0.7.19,netifaces==0.10.5,-e
>>> git+https://github.com/openstack/networking-sfc.git@c51052e3
>>> 748e917731f449b0ff4dc20d2e484490#egg=networking_sfc,-e git+
>>> https://github.com/openstack/neutron.git@41be555eddb0f99
>>> 47fdaa4e73fa74a72677d4d11#egg=neutron,neutron-lib==1.2.0,ope
>>> nstackdocstheme==1.6.1,openstacksdk==0.9.13,os-api-ref==1.3.
>>> 0,os-client-config==1.26.0,os-testr==0.8.0,osc-lib==1.3.0,os
>>> lo.concurrency==3.19.0,oslo.config==3.22.0,oslo.context==2.
>>> 12.1,oslo.db==4.17.0,oslo.i18n==3.13.0,oslo.log==3.21.0,oslo
>>> .messaging==5.18.0,oslo.middleware==3.23.1,oslo.policy==1.
>>> 19.0,oslo.reports==1.17.0,oslo.rootwrap==5.4.0,oslo.
>>> serialization==2.17.0,oslo.service==1.19.0,oslo.utils==3.
>>> 22.0,oslo.versionedobjects==1.22.0,oslosphinx==4.10.0,
>>> oslotest==2.14.0,ovs==2.7.0,packaging==16.8,paramiko==2.1.
>>> 2,Paste==2.0.3,PasteDeploy==1.5.2,pbr==2.0.0,pecan==1.2.1,
>>> pep8==1.5.7,pika==0.10.0,pika-pool==0.1.3,positional==1.1.1,
>>> prettytable==0.7.2,psutil==5.2.0,psycopg2==2.7,pyasn1==0.2.
>>> 3,pycadf==2.5.0,pycparser==2.17,pyflakes==0.8.1,Pygments==
>>> 2.2.0,pyinotify==0.9.6,pylint==1.4.5,PyMySQL==0.7.10,
>>> pyparsing==2.2.0,python-cinderclient==1.11.0,python-
>>> dateutil==2.6.0,python-designateclient==2.6.0,python-editor=
>>> =1.0.3,pytho

Re: [openstack-dev] [networking-sfc] patch test failed due to "import error: vlanmanager"

[Vikash Kumar]

Hi Igor,

   This is weird. I just did a fresh clone and executed *"tox" *command. I
am getting same error. Am I missing anything here ? There is no private
change here.  Below is the link for entire log.

 http://paste.openstack.org/show/601870/

On Tue, Mar 7, 2017 at 10:46 PM, Duarte Cardoso, Igor <
igor.duarte.card...@intel.com> wrote:

> Hi Vikash,
>
> Please stick to pastebin for complete logs.
>
>
>
> Check your migration files:
>
>
>
> FAILED: Contract HEAD file does not match migration timeline head,
> expected: 48072cb59133
>
>
>
> Best regards,
>
> Igor.
>
>
>
> *From:* Vikash Kumar [mailto:vikash.ku...@oneconvergence.com]
> *Sent:* Tuesday, March 7, 2017 5:03 PM
> *To:* openstack-dev <openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [networking-sfc] patch test failed due to
> "import error: vlanmanager"
>
>
>
> Complete log:
>
>  py35 create: /home/vikash/guess_vk/python-dev/networking-sfc/.tox/py35
> py35 installdeps: 
> -r/home/vikash/guess_vk/python-dev/networking-sfc/requirements.txt,
> -r/home/vikash/guess_vk/python-dev/networking-sfc/test-requirements.txt
> py35 develop-inst: /home/vikash/guess_vk/python-dev/networking-sfc
> py35 installed: 
> /home/vikash/guess_vk/python-dev/networking-sfc/.tox/py35/lib/python3.5/site.py:165:
> DeprecationWarning: 'U' mode is deprecated,  f = open(fullname,
> "rU"),alabaster==0.7.10,alembic==0.9.1,amqp==1.4.9,
> anyjson==0.3.3,appdirs==1.4.2,astroid==1.3.8,Babel==2.3.4,
> beautifulsoup4==4.5.3,cachetools==2.0.0,cffi==1.9.1,
> cliff==2.4.0,cmd2==0.7.0,contextlib2==0.5.4,coverage==
> 4.3.4,cryptography==1.7.2,debtcollector==1.12.0,
> decorator==4.0.11,docutils==0.13.1,dulwich==0.17.1,eventlet=
> =0.19.0,extras==1.0.0,fasteners==0.14.1,fixtures==3.
> 0.0,flake8==2.5.5,futurist==0.21.0,greenlet==0.4.12,hacking=
> =0.12.0,httplib2==0.10.3,idna==2.4,imagesize==0.7.1,iso8601=
> =0.1.11,Jinja2==2.9.5,jsonpatch==1.15,jsonpointer==1.10,jsonschema==2.6.0,
> keystoneauth1==2.18.0,keystonemiddleware==4.14.0,
> kombu==3.0.37,linecache2==1.0.0,logilab-common==1.3.0,
> logutils==0.3.4.1,Mako==1.0.6,MarkupSafe==0.23,mccabe==0.2.
> 1,mock==2.0.0,monotonic==1.2,mox3==0.20.0,msgpack-python==
> 0.4.8,netaddr==0.7.19,netifaces==0.10.5,-e git+https://github.com/
> openstack/networking-sfc.git@c51052e3748e917731f449b0ff4dc2
> 0d2e484490#egg=networking_sfc,-e git+https://github.com/
> openstack/neutron.git@41be555eddb0f9947fdaa4e73fa74a
> 72677d4d11#egg=neutron,neutron-lib==1.2.0,openstackdocstheme==1.6.1,
> openstacksdk==0.9.13,os-api-ref==1.3.0,os-client-config==
> 1.26.0,os-testr==0.8.0,osc-lib==1.3.0,oslo.concurrency==
> 3.19.0,oslo.config==3.22.0,oslo.context==2.12.1,oslo.db==
> 4.17.0,oslo.i18n==3.13.0,oslo.log==3.21.0,oslo.messaging==5.
> 18.0,oslo.middleware==3.23.1,oslo.policy==1.19.0,oslo.
> reports==1.17.0,oslo.rootwrap==5.4.0,oslo.serialization==2.
> 17.0,oslo.service==1.19.0,oslo.utils==3.22.0,oslo.
> versionedobjects==1.22.0,oslosphinx==4.10.0,oslotest==
> 2.14.0,ovs==2.7.0,packaging==16.8,paramiko==2.1.2,Paste==2.
> 0.3,PasteDeploy==1.5.2,pbr==2.0.0,pecan==1.2.1,pep8==1.5.7,
> pika==0.10.0,pika-pool==0.1.3,positional==1.1.1,prettytable=
> =0.7.2,psutil==5.2.0,psycopg2==2.7,pyasn1==0.2.3,pycadf==2.
> 5.0,pycparser==2.17,pyflakes==0.8.1,Pygments==2.2.0,
> pyinotify==0.9.6,pylint==1.4.5,PyMySQL==0.7.10,pyparsing==
> 2.2.0,python-cinderclient==1.11.0,python-dateutil==2.6.0,
> python-designateclient==2.6.0,python-editor==1.0.3,python-
> glanceclient==2.6.0,python-keystoneclient==3.10.0,python-
> mimeparse==1.6.0,python-neutronclient==6.1.0,python-
> novaclient==7.1.0,python-openstackclient==3.8.1,python-
> subunit==1.2.0,pytz==2016.10,PyYAML==3.12,reno==2.1.2,
> repoze.lru==0.6,requests==2.12.5,requests-mock==1.3.0,
> requestsexceptions==1.2.0,retrying==1.3.3,rfc3986==0.4.
> 1,Routes==2.4.1,ryu==4.12,simplejson==3.10.0,six==1.10.
> 0,snowballstemmer==1.2.1,Sphinx==1.5.3,SQLAlchemy==1.0.
> 17,sqlalchemy-migrate==0.11.0,sqlparse==0.2.3,statsd==3.2.1,
> stevedore==1.21.0,tempest-lib==1.0.0,Tempita==0.5.2,tenacity==3.7.1,
> testrepository==0.0.20,testresources==2.0.1,testscenarios==0.5.0,
> testtools==2.2.0,tinyrpc==0.5,traceback2==1.4.0,unittest2==
> 1.1.0,waitress==1.0.2,warlock==1.2.0,WebOb==1.6.3,WebTest==
> 2.0.26,wrapt==1.10.8
> py35 runtests: PYTHONHASHSEED='177840'
> py35 runtests: commands[0] | find . -type f -name *.py[c|o] -delete
> py35 runtests: commands[1] | find . -type d -name __pycache__ -delete
> py35 runtests: commands[2] | /home/vikash/guess_vk/python-
> dev/networking-sfc/tools/ostestr_compat_shim.sh
> /home/vikash/guess_vk/python-dev/networking-sfc/.tox/py35/lib/python3.5/site.py:165:
> DeprecationWa

Re: [openstack-dev] [networking-sfc] patch test failed due to "import error: vlanmanager"

[Vikash Kumar]

estrepository==0.0.20,testresources==2.0.1,testscenarios==0.5.0,testtools==2.2.0,tinyrpc==0.5,traceback2==1.4.0,unicodecsv==0.14.1,unittest2==1.1.0,waitress==1.0.2,warlock==1.2.0,WebOb==1.6.3,WebTest==2.0.26,wrapt==1.10.8
pylint runtests: PYTHONHASHSEED='177840'
pylint runtests: commands[0] | pylint --rcfile=.pylintrc
--output-format=colorized networking_sfc
* Module
networking_sfc.services.sfc.agent.extensions.openvswitch.sfc_driver
E: 23, 0: No name 'vlanmanager' in module
'neutron.plugins.ml2.drivers.openvswitch.agent' (no-name-in-module)
ERROR: InvocationError:
'/home/vikash/guess_vk/python-dev/networking-sfc/.tox/pylint/bin/pylint
--rcfile=.pylintrc --output-format=colorized networking_sfc'
_
summary
_
ERROR:   py35: commands failed
ERROR:   py27: commands failed
ERROR:   pep8: commands failed
ERROR:   pylint: commands failed


On Tue, Mar 7, 2017 at 9:35 PM, Vikash Kumar <
vikash.ku...@oneconvergence.com> wrote:

> Hi,
>
> I was testing patch on master branch, but the test is failing because
> of the import error.
>
> http://paste.openstack.org/show/601794/
>
> --
> Regards,
> Vikash
>



-- 
Regards,
Vikash
__
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-dev] [networking-sfc] patch test failed due to "import error: vlanmanager"

[Vikash Kumar]

Hi,

I was testing patch on master branch, but the test is failing because
of the import error.

http://paste.openstack.org/show/601794/

-- 
Regards,
Vikash
__
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

Re: [Openstack] [openstack-dev][neutron] Neutron firewall

[Vikash Kumar]

We have deployed VYOS Firewall in deployment with the current scope of APIs
somewhat like Van mentioned in his mail. But my experience says the current
FWaaS API  still need work for most of cloud deployment.

On Wed, Feb 1, 2017 at 3:36 PM, Jose Manuel Ferrer Mosteiro <
jmferrer.paradigmatecnolog...@gmail.com> wrote:

> Hi
>
> Firewall policies can be implemented with security groups.
>
> You can create as many isolated networks and routers as you want so an
> instance can be isolated in its own network ... but I prefer using security
> groups and creating a network for service (kubernetes: master network,
> minion project1 network, minion project2 network ...).
>
> When a server with ip 192.168.56.11 and MAC FA:16:3E:0F:67:90 is created,
> this rule is added automatically with default kvm hypervisor:
>
> Chain neutron-openvswi-sbd739c19-e (1 references)
> target prot opt source   destination
> RETURN all  --  192.168.56.11anywhere MAC
> FA:16:3E:0F:67:90 /* Allow traffic from defined IP/MAC pairs. */
> DROP   all  --  anywhere anywhere /* Drop
> traffic without an IP/MAC allow rule. */
>
> So you cannot set other ip address in port unless you set it with
> something like:
>
> neutron port-update 37f2d07e-4133-478c-b50d-39068adc8c3f
> --allowed-address-pairs type=dict list=true ip_address=192.168.56.11,ip_
> address=192.168.56.22
>
> It can be useful to deploy a pacemaker cluster with a cluster IP address.
>
>
>
> What other feature do you need?
>
>
>
> Jose Manuel
>
>
>
>
>
>
>
>
> El 2017-01-31 16:20, Cesar Benito Hernández escribió:
>
> We currently have a cloud infrastructure meeting our own requirements.
> Let's focus on some Networking features (firewall, instances isolation,
> spoofing control). We are thinking about moving to OpenStack and when we
> focus on these Networking features, Neutron comes into play. We are
> currently using Vyattas for these networking features (firewall, instance
> isolation, spoofing control) and we would like to keep it as it is right
> now. Therefore, if we move to OpenStack we would like Neutron to
> orchestrate these Vyattas but these Vyattas would be installed/configured
> in an outter layer, out of OpenStack. A good comparison we find is Cinder.
> In Cinder you can configure your storage backend (this storage backend is
> an external "agent" to OpenStack) and the idea with this networking
> features would be the same (being able to configure in Neutron our firewall
> backend).
>
> This is our desired scenario, and these are the questions that we arise.
> We would appreciate very much your feedback:
>
> - We believe the current Neutron FWaaS does not meet our requirement. It's
> not able to "talk" to an external firewall "backend". Are we right?
> - In case FWaaS does not meet our requirements, we can think of
> implementing/modifying the Neutron source code. I don't know exactly what
> this implies, but if we are in the right direction, a new Neutron API set
> of methods would be needed. Do you think the OpenStack community would
> accept this change?
> - Again, if we are right, apart from changing the Neutron source code to
> make it able to "talk" to an external firewall, we would also need to
> implement the firewall driver that matches the new API set of methods with
> the corresponding methods of the vendor's API (in our case Vyatta). Are we
> right?
>
> If you think this is a wrong forum to discuss all these questions, please,
> could you tell us another place to discuss all this?
>
> Thank you very much for your help and attention. We appreciate it.
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>


-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [neutron-fwaas] issue with firewall and sfc

[Vikash Kumar]

I will be happy to contribute and will join the meeting.

On Tue, Jan 31, 2017 at 8:36 PM, Sridar Kandaswamy (skandasw) <
skand...@cisco.com> wrote:

> Hi Vikash:
>
> The support for VM ports is in progress and we should have that completed
> fairly early in Pike. We have had some prelim thoughts on integration with
> SFC but have not come to that point yet. If u have some interest, u are
> also welcome to join our weekly meeting [1] and we can discuss more.
>
> Thanks
>
> Sridar
>
> [1] http://eavesdrop.openstack.org/#Firewall_as_a_Service_(
> FWaaS)_Team_Meeting
>
> From: Vikash Kumar <vikash.ku...@oneconvergence.com>
> Reply-To: OpenStack List <openstack-dev@lists.openstack.org>
> Date: Tuesday, January 31, 2017 at 2:49 AM
> To: OpenStack List <openstack-dev@lists.openstack.org>
> Subject: [openstack-dev] [neutron-fwaas] issue with firewall and sfc
>
> Hi,
>
>I am looking to fwaas_v2, which now allows the firewall rules to get
> apply on VM ports also. The doc suggests it will work in tandem with
> neutron SFC. However, in SFC the port-security is disabled and if thats the
> case, where will the IPTABLE rules will be rendered ?
>
> --
> Regards,
> Vikash
>
> __
> 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
>
>


-- 
Regards,
Vikash
__
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-dev] [neutron-fwaas] issue with firewall and sfc

[Vikash Kumar]

Hi,

   I am looking to fwaas_v2, which now allows the firewall rules to get
apply on VM ports also. The doc suggests it will work in tandem with
neutron SFC. However, in SFC the port-security is disabled and if thats the
case, where will the IPTABLE rules will be rendered ?

-- 
Regards,
Vikash
__
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

Re: [openstack-dev] [networking-sfc] Does SFC support chaining of Layer 2 devices?

[Vikash Kumar]

Louis,

   Typical L2 IDS devices mostly work in transparent/TAP mode which means
traffic is diverted to these devices without manipulating any packet
header. Interfaces/Ports of these devices are in promiscuous mode. Based on
the filtering rules , these devices take action on packets, most commonly
drop if found malicious otherwise sent out through outgoing interface.





On Sat, Jan 21, 2017 at 12:04 AM, Henry Fourie <louis.fou...@huawei.com>
wrote:

> Vikash,
>
>Unclear what you mean by SFC spinning an L2 IDS?
>
> What is the behavior of L2 IDS devices?
>
> -    Louis
>
>
>
> *From:* Vikash Kumar [mailto:vikash.ku...@oneconvergence.com]
> *Sent:* Wednesday, January 18, 2017 10:49 PM
> *To:* openstack-dev
> *Subject:* [openstack-dev] [networking-sfc] Does SFC support chaining of
> Layer 2 devices?
>
>
>
> All,
>
>I am exploring SFC for chaining an IDS device (strictly in L2 mode). As
> of now, it looks SFC default supports only L3 devices. SFC APIs doesn't
> have any way to specify the nature of device and without that, it seems
> there is no way an operator can spin any device/VNF except L3 mode VNFs. Is
> anything I am missing here ? Can one still spin a L2 IDS with SFC ?
>
>
>
> --
>
> Regards,
>
> Vikash
>
> __
> 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
>
>


-- 
Regards,
Vikash
__
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

Re: [Openstack] [devstack] Default devstack guest does not respond to ping/ssh

[Vikash Kumar]

On Tue, Jan 17, 2017 at 2:17 AM, Adam Kimball 
wrote:

> Greetings,
>
> I've been attempting to get a working devstack configuration for a few
> days no, and have been running into issues with networking. Specifically,
> after creating a local server, I've been unable to connect to it using a
> public interface from the same machine. Here are the steps I've attempted
> thus far:
>
>
>- Run devstack via stack.sh, with passwords correctly initialized
>   - Note: upon completion, there are two 'default' security group
>   entries listed when running 'openstack security group list'.
>- On both security groups, rules were created in an attempt to allow
>ssh and ping
>   - openstack security group rule create $secgroup_uuid --protocol
>   tcp --dst-port 22 --remote-ip 0.0.0.0/0
>   - openstack security group rule create $secgroup_uuid --protocol
>   udp --dst-port 22 --remote-ip 0.0.0.0/0
>   - openstack security group rule create $secgroup_uuid --protocol
>   icmp --dst-port -1 --remote-ip 0.0.0.0/0
>- We then launch an instance
>   - openstack server create --image cirros-0.3.4-x86_64-uec --flavor
>   m1.medium test
>- This instance seems to launch fully. It has an address from the
>network named 'public'.
>
>
​'public' networks are external and if your intention is to get
public ip for ur instances then create a provider network instead , create
a subnet in it and assign it the range of free IP in your network. Now,
once you have network in place make sure you map it to correct interface of
the host . Now you can boot the VM with the network you just created and it
will get one of your public IP.

Other way is created a private network. Boot VM on this network. Create
external network and assign a pool of free IPs on your public network.
Create router and do the needed. Create a FIP and attach it to VM. Its done
your VM has now external connectivity.

 Hope this help.

>
>-
>   - However, according to the logs, as it's coming up, DHCP seems to
>   fail!
>   - I have also tried with Ubuntu, rather than cirros, to check for
>   image corruption.
>
> As a result, I'm unable to ping or ssh into the instance. Any thoughts or
> helpful comments?
>
> Thanks,
> Adam Kimball
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
>
>


-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] How to troubleshoot Security Group rules

[Vikash Kumar]

Checkout on the bridge connected to tap ports.

On Thu, Jan 19, 2017 at 7:02 PM, Vimal Kumar  wrote:

> Hi,
>
> Is the rules implemented in the iptables of the node (I am running
> all-in-one, LinuxBridge setup), or is it implemented in the iptables of a
> separate network namespace?
>
> On Thu, Jan 19, 2017 at 1:27 PM, Melvin Hillsman 
> wrote:
>
>> If you are running an all-in-one/single node deployment, your security
>> groups are implemented via iptables on that node. If you had a multi-node
>> setup, security group rules would show up on the compute hosts.
>>
>> On Thu, Jan 19, 2017 at 12:47 AM, Vimal Kumar 
>> wrote:
>>
>>> Hi!
>>>
>>> How can I troubleshoot issues related to security groups? It is probably
>>> getting implemented via iptables but where? In the host iptables, or inside
>>> network namespace, or inside instance itself? I am running a single-node
>>> Newton.
>>>
>>> I am looking for a way to check whether the rules in my security group
>>> is actually being implemented or not.
>>>
>>> Thank you!
>>>
>>> Regards,
>>>
>>> Vimal
>>>
>>> ___
>>> Mailing list: http://lists.openstack.org/cgi
>>> -bin/mailman/listinfo/openstack
>>> Post to : openstack@lists.openstack.org
>>> Unsubscribe : http://lists.openstack.org/cgi
>>> -bin/mailman/listinfo/openstack
>>>
>>>
>>
>>
>> --
>> Kind regards,
>>
>> Melvin Hillsman
>> Ops Technical Lead
>> OpenStack Innovation Center
>>
>> mrhills...@gmail.com
>> phone: (210) 312-1267
>> mobile: (210) 413-1659
>> http://osic.org
>>
>> Learner | Ideation | Belief | Responsibility | Command
>>
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>


-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [networking-sfc] Does SFC support chaining of Layer 2 devices?

[Vikash Kumar]

On Thu, Jan 19, 2017 at 12:18 PM, Vikash Kumar <
vikash.ku...@oneconvergence.com> wrote:

> All,
>
>I am exploring SFC for chaining an IDS device (strictly in L2 mode). As
> of now, it looks SFC default supports only L3 devices. SFC APIs doesn't
> have any way to specify the nature of device and without that, it seems
> there is no way an operator can spin any device/VNF except L3 mode VNFs. Is
> anything I am missing here ? Can one still spin a L2 IDS with SFC ?
>
>
> --
> Regards,
> Vikash
>



-- 
Regards,
Vikash
__
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-dev] [networking-sfc] Does SFC support chaining of Layer 2 devices?

[Vikash Kumar]

All,

   I am exploring SFC for chaining an IDS device (strictly in L2 mode). As
of now, it looks SFC default supports only L3 devices. SFC APIs doesn't
have any way to specify the nature of device and without that, it seems
there is no way an operator can spin any device/VNF except L3 mode VNFs. Is
anything I am missing here ? Can one still spin a L2 IDS with SFC ?


-- 
Regards,
Vikash
__
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

Re: [Openstack] [networking-sfc] SFC in BITW or L2 mode

[Vikash Kumar]

If thats the case then does it only support L3 mode as of now? My
experiment suggest same. With this limitation, it won't be possible to any
L2/BITW network functions.

On Tue, Jan 10, 2017 at 12:59 PM, Vikram Choudhary <viks...@gmail.com>
wrote:

> networking-sfc doesn't care about the VNF deployment mode. If you see the
> API's, it's all about chaining neutron ports..
>
> On Tue, Jan 10, 2017 at 12:26 PM, Vikash Kumar <
> vikash.ku...@oneconvergence.com> wrote:
>
>> Which API specifies the mode of VNF (L3/L2/BITW) ? I need to insert a
>> Firewall in L2 mode.
>>
>> --
>> Regards,
>> Vikash
>>
>> ___
>> Mailing list: http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>>
>>
>


-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [networking-sfc] SFC in BITW or L2 mode

[Vikash Kumar]

On Tue, Jan 10, 2017 at 12:26 PM, Vikash Kumar <
vikash.ku...@oneconvergence.com> wrote:

> Which API specifies the mode of VNF (L3/L2/BITW) ? I need to insert a
> Firewall in L2 mode.
>
> --
> Regards,
> Vikash
>



-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [networking-sfc] SFC in BITW or L2 mode

[Vikash Kumar]

Which API specifies the mode of VNF (L3/L2/BITW) ? I need to insert a
Firewall in L2 mode.

-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [neutron][oslo]neutron agent not receiving callback

[Vikash Kumar]

Thanks,

 Yeah I just gone over doc. and tried to use the subscription. After
looking into code I understood thats its not for interprocess.

@Armando - Thanks for updating faq

On Wed, Mar 9, 2016 at 10:40 PM, Armando M. <arma...@gmail.com> wrote:

>
>
> On 9 March 2016 at 09:14, Assaf Muller <as...@redhat.com> wrote:
>
>> On Wed, Mar 9, 2016 at 9:40 AM, Ihar Hrachyshka <ihrac...@redhat.com>
>> wrote:
>> > Vikash Kumar <vikash.ku...@oneconvergence.com> wrote:
>> >
>> >>
>> >>
>> >> On Wed, Mar 9, 2016 at 3:42 PM, Vikash Kumar
>> >> <vikash.ku...@oneconvergence.com> wrote:
>> >> I have written a sample neutron agent which subscribe for the
>> AFTER_CREATE
>> >> event of router. I have defined a sample method as callback, but the
>> method
>> >> doesn't gets called anytime.
>> >>
>> >> Also, in logs:
>> >>
>> >> 2016-03-09 01:36:08.220 7075 DEBUG neutron.callbacks.manager [-]
>> >> Subscribe:  router after_create
>> >> subscribe /opt/stack/neutron/neutron/callbacks/manager.py:41
>> >>
>> >>
>> >> which means the subscription is successful.
>> >>
>> >>Do I need to enable anything in config file to get that ? Or am I
>> >> missing something ?
>> >
>> >
>> > First, nothing oslo specific is discussed here, so [oslo] tag is
>> probably
>> > redundant.
>> >
>> > Overall, I believe you try to rely on wrong thing that won’t deliver for
>> > you: callbacks are internal to neutron-server, so events triggered by
>> > neutron-servers will never reach any other processes (like your agent).
>>
>> The same callbacks mechanism is also used in the L3 agent, but as Ihar
>> said, events in one process (neutron-server) will not trigger
>> callbacks in another process (l3-agent). If that's what you want,
>> you'll need RPC.
>>
>
> Callbacks is a general pub/sub local communication mechanism, whether it
> applies to neutron-server or an agent. Clarifying here:
>
> https://review.openstack.org/#/c/290700/
>
>
>>
>> >
>> > More info:
>> http://docs.openstack.org/developer/neutron/devref/callbacks.html
>> >
>> > Ihar
>> >
>> >
>> __
>> > 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 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 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
>
>


-- 
Regards,
Vikash
__
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] [neutron][oslo]neutron agent not receiving callback

[Vikash Kumar]

On Wed, Mar 9, 2016 at 3:42 PM, Vikash Kumar <
vikash.ku...@oneconvergence.com> wrote:

> I have written a sample neutron agent which subscribe for the AFTER_CREATE
> event of router. I have defined a sample method as callback, but the method
> doesn't gets called anytime.
>
> Also, in logs:
>
> 2016-03-09 01:36:08.220 7075 DEBUG neutron.callbacks.manager [-]
> Subscribe:  router after_create
> subscribe /opt/stack/neutron/neutron/callbacks/manager.py:41
>
>
> which means the subscription is successful.
>
>Do I need to enable anything in config file to get that ? Or am I
> missing something ?
>
> --
> Regards,
> Vikash
>



-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[openstack-dev] [neutron][oslo]neutron agent not receiving callback

[Vikash Kumar]

On Wed, Mar 9, 2016 at 3:42 PM, Vikash Kumar <
vikash.ku...@oneconvergence.com> wrote:

> I have written a sample neutron agent which subscribe for the AFTER_CREATE
> event of router. I have defined a sample method as callback, but the method
> doesn't gets called anytime.
>
> Also, in logs:
>
> 2016-03-09 01:36:08.220 7075 DEBUG neutron.callbacks.manager [-]
> Subscribe:  router after_create
> subscribe /opt/stack/neutron/neutron/callbacks/manager.py:41
>
>
> which means the subscription is successful.
>
>Do I need to enable anything in config file to get that ? Or am I
> missing something ?
>
> --
> Regards,
> Vikash
>



-- 
Regards,
Vikash
__
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] neutron agent not receiving callback

[Vikash Kumar]

I have written a sample neutron agent which subscribe for the AFTER_CREATE
event of router. I have defined a sample method as callback, but the method
doesn't gets called anytime.

Also, in logs:

2016-03-09 01:36:08.220 7075 DEBUG neutron.callbacks.manager [-] Subscribe:
 router after_create subscribe
/opt/stack/neutron/neutron/callbacks/manager.py:41


which means the subscription is successful.

   Do I need to enable anything in config file to get that ? Or am I
missing something ?

-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[openstack-dev] neutron agent not receiving callback

[Vikash Kumar]

I have written a sample neutron agent which subscribe for the AFTER_CREATE
event of router. I have defined a sample method as callback, but the method
doesn't gets called anytime.

Also, in logs:

2016-03-09 01:36:08.220 7075 DEBUG neutron.callbacks.manager [-] Subscribe:
 router after_create subscribe
/opt/stack/neutron/neutron/callbacks/manager.py:41


which means the subscription is successful.

   Do I need to enable anything in config file to get that ? Or am I
missing something ?

-- 
Regards,
Vikash
__
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] [openstack-dev][oslo] Exception in rpc_dispatcher

[Vikash Kumar]

Hi,

   I am getting this error in my agent side. I am getting same message
twice, one after other.

2015-05-07 11:39:28.189 11363 ERROR oslo.messaging.rpc.dispatcher
[req-43875dc3-99a9-4803-aba2-5cff22943c2c ] Exception during message
handling: _oslo_messaging_localcontext_7a1e392197394132b7bfc1bda8239a82
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher Traceback
(most recent call last):
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher   File
/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line
134, in _dispatch_and_reply
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
incoming.message))
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher   File
/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line
179, in _dispatch
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
localcontext.clear_local_context()
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher   File
/usr/lib/python2.7/dist-packages/oslo/messaging/localcontext.py, line 55,
in clear_local_context
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
delattr(_STORE, _KEY)
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
AttributeError:
_oslo_messaging_localcontext_7a1e392197394132b7bfc1bda8239a82
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher

-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [oslo] Exception in rpc_dispatcher

[Vikash Kumar]

I did following in my agent code:

import eventlet

eventlet.monkey_patch()

but still I see same issue.

On Thu, May 7, 2015 at 1:22 PM, Mehdi Abaakouk sil...@sileht.net wrote:


 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256

 Hi,

 This is a well known issue when eventlet monkey patching is not done
 correctly.
 The application must do the monkey patching before anything else even
 loading another module that eventlet.

 You can find more information here:
 https://bugs.launchpad.net/oslo.messaging/+bug/1288878

 Or some examples of how nova and ceilometer ensure that:

  https://github.com/openstack/nova/blob/master/nova/cmd/__init__.py

 https://github.com/openstack/ceilometer/blob/master/ceilometer/cmd/__init__.py


 More recent version of oslo.messaging already outputs a better error
 message in this case.

 Cheers,

 - ---
 Mehdi Abaakouk
 mail: sil...@sileht.net
 irc: sileht



 Le 2015-05-07 08:11, Vikash Kumar a écrit :

 Hi,

I am getting this error in my agent side. I am getting same message
 twice, one after other.

 2015-05-07 11:39:28.189 11363 ERROR oslo.messaging.rpc.dispatcher
 [req-43875dc3-99a9-4803-aba2-5cff22943c2c ] Exception during message
 handling: _oslo_messaging_localcontext_7a1e392197394132b7bfc1bda8239a82
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
 Traceback
 (most recent call last):
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher   File
 /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line
 134, in _dispatch_and_reply
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
 incoming.message))
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher   File
 /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line
 179, in _dispatch
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
 localcontext.clear_local_context()
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher   File
 /usr/lib/python2.7/dist-packages/oslo/messaging/localcontext.py, line
 55,
 in clear_local_context
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
 delattr(_STORE, _KEY)
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
 AttributeError:
 _oslo_messaging_localcontext_7a1e392197394132b7bfc1bda8239a82
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher

 __
 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

 -BEGIN PGP SIGNATURE-
 Version: OpenPGP.js v.1.20131017
 Comment: http://openpgpjs.org

 wsFcBAEBCAAQBQJVSxmkCRAYkrQvzqrryAAAcA4P/iTf59F9HbqQF6uuKDM6
 HMPWg0PovpzUg0opOMMBE8ZwiQ6B+w5MS3rkwDzbcXfqijDxM8A0BAOwG5/v
 iFGfENKPIVm2Y/7iHmg84+MXSKSYDNmsuZc0AOP0i9Ar9D6E8SZbC5hMSfAO
 KOZBbVmBP14/KhXesxJPx5nbDknhRPLravV9o/iyMnLSWBGQa80X92G1tkz6
 6PI/UCCp1SGyky0eg0ZoZ5+IX3r9UsyjGDRS+le+lQEu4T0e05G1jBnvw9H7
 qIo7ecWDSUwwxl7sz2HlgaF0st4bjCtRtSPbbcW2nShKBVbIdAxfncj2O8Ux
 PVwk4ZaEdyQ+O2RJp/vq6v9jcNsoh/3jCLojEwUv4BlLS7qEW4Ime0coJoxD
 zgC1vdgSojS8pxRto8kh7NJ91MpILRDfm3bJ/bpTGb04Wh4LYGHmoeQMrCex
 rPmYgDkWTXUpsqAgwHpP8DZpRXY40hx6yCiWp/1lNLI/CYx4B6fDOOS7Xf8k
 kjmRrzV8QriQ+02M9cCWIgLyskAUIWRzEn/ZhtAiQTvaCJEuMvQTHSYMf30J
 m1hW2bL5UcuwA+4Or6nxzfF14EDaWZv2dD2hPNvfJ3qMXgCHQoQUVp061sto
 p7RPmzWVWuNrwmVIp0JcJSLDGRSifGadDw/3Uiygpo9M9RfUJEpC2RJ85WjU
 DSE8
 =nSuZ
 -END PGP SIGNATURE-


 __
 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




-- 
Regards,
Vikash
__
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

Re: [Openstack] [openstack-dev] [oslo] Exception in rpc_dispatcher

[Vikash Kumar]

I did following in my agent code:

import eventlet

eventlet.monkey_patch()

but still I see same issue.

On Thu, May 7, 2015 at 1:22 PM, Mehdi Abaakouk sil...@sileht.net wrote:


 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256

 Hi,

 This is a well known issue when eventlet monkey patching is not done
 correctly.
 The application must do the monkey patching before anything else even
 loading another module that eventlet.

 You can find more information here:
 https://bugs.launchpad.net/oslo.messaging/+bug/1288878

 Or some examples of how nova and ceilometer ensure that:

  https://github.com/openstack/nova/blob/master/nova/cmd/__init__.py

 https://github.com/openstack/ceilometer/blob/master/ceilometer/cmd/__init__.py


 More recent version of oslo.messaging already outputs a better error
 message in this case.

 Cheers,

 - ---
 Mehdi Abaakouk
 mail: sil...@sileht.net
 irc: sileht



 Le 2015-05-07 08:11, Vikash Kumar a écrit :

 Hi,

I am getting this error in my agent side. I am getting same message
 twice, one after other.

 2015-05-07 11:39:28.189 11363 ERROR oslo.messaging.rpc.dispatcher
 [req-43875dc3-99a9-4803-aba2-5cff22943c2c ] Exception during message
 handling: _oslo_messaging_localcontext_7a1e392197394132b7bfc1bda8239a82
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
 Traceback
 (most recent call last):
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher   File
 /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line
 134, in _dispatch_and_reply
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
 incoming.message))
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher   File
 /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line
 179, in _dispatch
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
 localcontext.clear_local_context()
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher   File
 /usr/lib/python2.7/dist-packages/oslo/messaging/localcontext.py, line
 55,
 in clear_local_context
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
 delattr(_STORE, _KEY)
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
 AttributeError:
 _oslo_messaging_localcontext_7a1e392197394132b7bfc1bda8239a82
 2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher

 __
 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

 -BEGIN PGP SIGNATURE-
 Version: OpenPGP.js v.1.20131017
 Comment: http://openpgpjs.org

 wsFcBAEBCAAQBQJVSxmkCRAYkrQvzqrryAAAcA4P/iTf59F9HbqQF6uuKDM6
 HMPWg0PovpzUg0opOMMBE8ZwiQ6B+w5MS3rkwDzbcXfqijDxM8A0BAOwG5/v
 iFGfENKPIVm2Y/7iHmg84+MXSKSYDNmsuZc0AOP0i9Ar9D6E8SZbC5hMSfAO
 KOZBbVmBP14/KhXesxJPx5nbDknhRPLravV9o/iyMnLSWBGQa80X92G1tkz6
 6PI/UCCp1SGyky0eg0ZoZ5+IX3r9UsyjGDRS+le+lQEu4T0e05G1jBnvw9H7
 qIo7ecWDSUwwxl7sz2HlgaF0st4bjCtRtSPbbcW2nShKBVbIdAxfncj2O8Ux
 PVwk4ZaEdyQ+O2RJp/vq6v9jcNsoh/3jCLojEwUv4BlLS7qEW4Ime0coJoxD
 zgC1vdgSojS8pxRto8kh7NJ91MpILRDfm3bJ/bpTGb04Wh4LYGHmoeQMrCex
 rPmYgDkWTXUpsqAgwHpP8DZpRXY40hx6yCiWp/1lNLI/CYx4B6fDOOS7Xf8k
 kjmRrzV8QriQ+02M9cCWIgLyskAUIWRzEn/ZhtAiQTvaCJEuMvQTHSYMf30J
 m1hW2bL5UcuwA+4Or6nxzfF14EDaWZv2dD2hPNvfJ3qMXgCHQoQUVp061sto
 p7RPmzWVWuNrwmVIp0JcJSLDGRSifGadDw/3Uiygpo9M9RfUJEpC2RJ85WjU
 DSE8
 =nSuZ
 -END PGP SIGNATURE-


 __
 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




-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[openstack-dev] [oslo] Exception in rpc_dispatcher

[Vikash Kumar]

Hi,

   I am getting this error in my agent side. I am getting same message
twice, one after other.

2015-05-07 11:39:28.189 11363 ERROR oslo.messaging.rpc.dispatcher
[req-43875dc3-99a9-4803-aba2-5cff22943c2c ] Exception during message
handling: _oslo_messaging_localcontext_7a1e392197394132b7bfc1bda8239a82
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher Traceback
(most recent call last):
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher   File
/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line
134, in _dispatch_and_reply
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
incoming.message))
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher   File
/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line
179, in _dispatch
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
localcontext.clear_local_context()
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher   File
/usr/lib/python2.7/dist-packages/oslo/messaging/localcontext.py, line 55,
in clear_local_context
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
delattr(_STORE, _KEY)
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher
AttributeError:
_oslo_messaging_localcontext_7a1e392197394132b7bfc1bda8239a82
2015-05-07 11:39:28.189 11363 TRACE oslo.messaging.rpc.dispatcher

-- 
Regards,
Vikash
__
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] How to set openstack agent's exchange to accept fanout cast message

[Vikash Kumar]

Hi,

I am writing a agent which need to receive the fanout cast message from
neutron plugin. How to enable exchange to receive fanout message?

-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[openstack-dev] [oslo] oslo error while changing the the topic of plugin.

[Vikash Kumar]

All,

   I changed the topic of firewall plugin and configured the agent to
listen on same topic. But i am getting this error while publishing the
message.

2015-04-29 18:12:55.464 31761 ERROR oslo.messaging._drivers.impl_rabbit
[req-97302491-1a34-45c1-931c-1115fc1b0674 ] Failed to publish message to
topic 'my_fw_agent': Exchange.declare: (406) PRECONDITION_FAILED - cannot
redeclare exchange 'oc_fw_agent_fanout' in vhost '/' with different type,
durable, internal or autodelete value
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
Traceback (most recent call last):
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
File
/usr/lib/python2.7/dist-packages/oslo/messaging/_drivers/impl_rabbit.py,
line 655, in ensure
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
return method()
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
File
/usr/lib/python2.7/dist-packages/oslo/messaging/_drivers/impl_rabbit.py,
line 752, in _publish
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
publisher = cls(self.conf, self.channel, topic=topic, **kwargs)
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
File
/usr/lib/python2.7/dist-packages/oslo/messaging/_drivers/impl_rabbit.py,
line 393, in __init__
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
None, type='fanout', **options)
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
File
/usr/lib/python2.7/dist-packages/oslo/messaging/_drivers/impl_rabbit.py,
line 326, in __init__
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
self.reconnect(channel)
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
File
/usr/lib/python2.7/dist-packages/oslo/messaging/_drivers/impl_rabbit.py,
line 334, in reconnect
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
routing_key=self.routing_key)
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
File /usr/lib/python2.7/dist-packages/kombu/messaging.py, line 82, in
__init__
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
self.revive(self._channel)
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
File /usr/lib/python2.7/dist-packages/kombu/messaging.py, line 216, in
revive
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
self.declare()
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
File /usr/lib/python2.7/dist-packages/kombu/messaging.py, line 102, in
declare
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
self.exchange.declare()
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
File /usr/lib/python2.7/dist-packages/kombu/entity.py, line 166, in
declare
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
nowait=nowait, passive=passive,
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
File /usr/lib/python2.7/dist-packages/amqp/channel.py, line 620, in
exchange_declare
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
(40, 11),  # Channel.exchange_declare_ok
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
File /usr/lib/python2.7/dist-packages/amqp/abstract_channel.py, line 69,
in wait
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
return self.dispatch_method(method_sig, args, content)
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
File /usr/lib/python2.7/dist-packages/amqp/abstract_channel.py, line 87,
in dispatch_method
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
return amqp_method(self, args)
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
File /usr/lib/python2.7/dist-packages/amqp/channel.py, line 241, in _close
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
reply_code, reply_text, (class_id, method_id), ChannelError,
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
PreconditionFailed: Exchange.declare: (406) PRECONDITION_FAILED - cannot
redeclare exchange 'oc_fw_agent_fanout' in vhost '/' with different type,
durable, internal or autodelete value
2015-04-29 18:12:55.464 31761 TRACE oslo.messaging._drivers.impl_rabbit
2015-04-29 18:12:55.465 31761 INFO oslo.messaging._drivers.impl_rabbit
[req-97302491-1a34-45c1-931c-1115fc1b0674 ] Delaying reconnect for 1.0
seconds..

-- 
Regards,
Vikash
__
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

Re: [Openstack] ERROR: neutronclient.shell Quota exceeded for resources: ['security_group']

[Vikash Kumar]

Check ur neturon.conf file. Look for quota section, edit it and it will
work.

On Fri, Feb 6, 2015 at 8:32 AM, masoom alam masoom.a...@wanclouds.net
wrote:

 Hi every one

 I am getting the following exception in the command neutron
 security-group-create group

 *ERROR: neutronclient.shell Quota exceeded for resources*:
 ['security_group']
 Traceback (most recent call last):
   File /usr/local/lib/python2.7/dist-packages/neutronclient/shell.py,
 line 692, in run_subcommand
 return run_command(cmd, cmd_parser, sub_argv)
   File /usr/local/lib/python2.7/dist-packages/neutronclient/shell.py,
 line 91, in run_command
 return cmd.run(known_args)
   File
 /usr/local/lib/python2.7/dist-packages/neutronclient/common/command.py,
 line 29, in run
 return super(OpenStackCommand, self).run(parsed_args)
   File /usr/local/lib/python2.7/dist-packages/cliff/display.py, line 91,
 in run
 column_names, data = self.take_action(parsed_args)
   File
 /usr/local/lib/python2.7/dist-packages/neutronclient/common/command.py,
 line 35, in take_action
 return self.get_data(parsed_args)


 see the quoatas:

 nova quota-defaults
 +-+---+
 | Quota   | Limit |
 +-+---+
 | instances   | 10|
 | cores   | 20|
 | ram | 51200 |
 | floating_ips| 10|
 | fixed_ips   | -1|
 | metadata_items  | 128   |
 | injected_files  | 5 |
 | injected_file_content_bytes | 10240 |
 | injected_file_path_bytes| 255   |
 | key_pairs   | 700   |
 | security_groups | 700   |
 | security_group_rules| 700   |
 +-+---+





 ___
 Mailing list:
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
 Post to : openstack@lists.openstack.org
 Unsubscribe :
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack




-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [Openstack] Openstack Network Node High Availability [openstack]

[Vikash Kumar]

On Thu, Jan 29, 2015 at 11:46 AM, Chinasubbareddy M 
chinasubbaredd...@persistent.com wrote:

  Hi,



 As per my knowledge DVR is to avoid neutron node as an single point of
 failure and distribute l3 operations across compute nodes.


​ Thats correct, thats why I mentioned to some extent.​




 HA for L3 agents is working from Juno but it will be on active/passive
 mode, only one l3 will be on active at a time .


​ I don't think its a true deployable solution.​




 Subbareddy,

 Persistent systems ltd.



 *From:* Vikash Kumar [mailto:vikash.ku...@oneconvergence.com]
 *Sent:* Thursday, January 29, 2015 11:32 AM
 *To:* Openstack Milis; openstack-dev
 *Subject:* Re: [Openstack] [openstack-dev] Openstack Network Node High
 Availability [openstack]



 Is DVR a possible way to some extent(loosely)  to address HA of l3 agents ?



 On Thu, Jan 29, 2015 at 11:08 AM, Vikash Kumar 
 vikash.ku...@oneconvergence.com wrote:

 Hi,

 Is there any work going on High Availability of Network Node or is
 there any existing work? I see doc. on running multiple dhcp agent on
 multiple node but do not got on l3 agent. Is there any doc having details
 of running multiple dhcp agents on multiple hosts?


 --

 Regards,

 Vikash


 __
 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




 --

 Regards,

 Vikash

 DISCLAIMER == This e-mail may contain privileged and confidential
 information which is the property of Persistent Systems Ltd. It is intended
 only for the use of the individual or entity to which it is addressed. If
 you are not the intended recipient, you are not authorized to read, retain,
 copy, print, distribute or use this message. If you have received this
 communication in error, please notify the sender and delete all copies of
 this message. Persistent Systems Ltd. does not accept any liability for
 virus infected mails.




-- 
Regards,
Vikash
__
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

Re: [Openstack] [openstack-dev] Openstack Network Node High Availability [openstack]

[Vikash Kumar]

Is DVR a possible way to some extent(loosely)  to address HA of l3 agents ?

On Thu, Jan 29, 2015 at 11:08 AM, Vikash Kumar 
vikash.ku...@oneconvergence.com wrote:

 Hi,

 Is there any work going on High Availability of Network Node or is
 there any existing work? I see doc. on running multiple dhcp agent on
 multiple node but do not got on l3 agent. Is there any doc having details
 of running multiple dhcp agents on multiple hosts?

 --
 Regards,
 Vikash

 __
 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




-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack-dev] Openstack Network Node High Availability [openstack]

[Vikash Kumar]

On Thu, Jan 29, 2015 at 11:46 AM, Chinasubbareddy M 
chinasubbaredd...@persistent.com wrote:

  Hi,



 As per my knowledge DVR is to avoid neutron node as an single point of
 failure and distribute l3 operations across compute nodes.


​ Thats correct, thats why I mentioned to some extent.​




 HA for L3 agents is working from Juno but it will be on active/passive
 mode, only one l3 will be on active at a time .


​ I don't think its a true deployable solution.​




 Subbareddy,

 Persistent systems ltd.



 *From:* Vikash Kumar [mailto:vikash.ku...@oneconvergence.com]
 *Sent:* Thursday, January 29, 2015 11:32 AM
 *To:* Openstack Milis; openstack-dev
 *Subject:* Re: [Openstack] [openstack-dev] Openstack Network Node High
 Availability [openstack]



 Is DVR a possible way to some extent(loosely)  to address HA of l3 agents ?



 On Thu, Jan 29, 2015 at 11:08 AM, Vikash Kumar 
 vikash.ku...@oneconvergence.com wrote:

 Hi,

 Is there any work going on High Availability of Network Node or is
 there any existing work? I see doc. on running multiple dhcp agent on
 multiple node but do not got on l3 agent. Is there any doc having details
 of running multiple dhcp agents on multiple hosts?


 --

 Regards,

 Vikash


 __
 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




 --

 Regards,

 Vikash

 DISCLAIMER == This e-mail may contain privileged and confidential
 information which is the property of Persistent Systems Ltd. It is intended
 only for the use of the individual or entity to which it is addressed. If
 you are not the intended recipient, you are not authorized to read, retain,
 copy, print, distribute or use this message. If you have received this
 communication in error, please notify the sender and delete all copies of
 this message. Persistent Systems Ltd. does not accept any liability for
 virus infected mails.




-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[openstack-dev] Openstack Network Node High Availability [openstack]

[Vikash Kumar]

Hi,

Is there any work going on High Availability of Network Node or is
there any existing work? I see doc. on running multiple dhcp agent on
multiple node but do not got on l3 agent. Is there any doc having details
of running multiple dhcp agents on multiple hosts?

-- 
Regards,
Vikash
__
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] Openstack Network Node High Availability [openstack][openstack-dev]

[Vikash Kumar]

Hi,

Is there any work going on High Availability of Network Node or is
there any existing work? I see doc. on running multiple dhcp agent on
multiple node but do not got on l3 agent. Is there any doc having details
of running multiple dhcp agents on multiple hosts?

-- 
Regards,
Vikash
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] Openstack Network Node High Availability [openstack]

[Vikash Kumar]

Is DVR a possible way to some extent(loosely)  to address HA of l3 agents ?

On Thu, Jan 29, 2015 at 11:08 AM, Vikash Kumar 
vikash.ku...@oneconvergence.com wrote:

 Hi,

 Is there any work going on High Availability of Network Node or is
 there any existing work? I see doc. on running multiple dhcp agent on
 multiple node but do not got on l3 agent. Is there any doc having details
 of running multiple dhcp agents on multiple hosts?

 --
 Regards,
 Vikash

 __
 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




-- 
Regards,
Vikash
__
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-dev] libvirt memory ballooning [nova]

[Vikash Kumar]

All,

   There is blueprint for enabling  libvirt memory ballooning
https://blueprints.launchpad.net/nova/+spec/libvirt-memory-ballooning in
openstack nova. I think for Hyper-V , its already in place. Can we discuss
about the design and implementation and target for L release?


Regards,
Vikash
__
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

Re: [openstack-dev] [Openstack] [Nova] Launch of VM failed after certain count openstack Havana

[Vikash Kumar]

Hi Hrushikesh,

On Tue, Jul 8, 2014 at 10:53 AM, Gangur, Hrushikesh (R  D HP Cloud) 
hrushikesh.gan...@hp.com wrote:

  If it is not going to nova-compute, it must be thrown out directly at
 nova-api due to any of the following reasons:


May be, but even doesn't see nova-api error logs.

  1.   No valid host to launch the instance: Though you can see free
 memory on the compute node, but it does check for few more things: disk
 space and CPU. Please note that the disk space being looked at is the
 theoretical value.

 2.   The instance flavor type is incorrect. The image uploaded might
 have not been specified the right correct min. disk and min. memory needs.
 So, if you use tiny flavor and the image really requires more than 2 GB of
 root, it is going to fail.




I will check with the below command.


  You may like to run the following command:

 nova hypervisor-stats



 Regards~hrushi



 *From:* Vikash Kumar [mailto:vikash.ku...@oneconvergence.com]
 *Sent:* Monday, July 07, 2014 9:13 PM
 *To:* Openstack Milis; openstack-dev
 *Subject:* [Openstack] [Nova] Launch of VM failed after certain count
 openstack Havana



 Hi all,

 I am facing issue with VM launch. I am using openstack *Havana.* I
 have one compute node with following specification:

 root@compute-node:~# lscpu
 Architecture:  x86_64
 CPU op-mode(s):32-bit, 64-bit
 Byte Order:Little Endian
 CPU(s):8
 On-line CPU(s) list:   0-7
 Thread(s) per core:1
 Core(s) per socket:4
 Socket(s): 2
 NUMA node(s):  1
 Vendor ID: GenuineIntel
 CPU family:6
 Model: 15
 Stepping:  7
 CPU MHz:   1995.104
 BogoMIPS:  3990.02
 Virtualization:VT-x
 L1d cache: 32K
 L1i cache: 32K
 L2 cache:  4096K
 NUMA node0 CPU(s): 0-7

 root@compute-node:~# free -h
  total   used   free sharedbuffers cached
 Mem:   15G   1.5G14G 0B   174M   531M
 -/+ buffers/cache:   870M14G
 Swap:  15G 0B15G

  But I am not able to launch more than 12-14 VM. VM launch fails. Even I
 don't see *ERROR *logs in any of nova logs on both *openstack controller
 and compute node.* Don't see any request coming to compute node also. I
 just tailed nova compute logs on compute node. As soon as, I clean the
 previous VMs , everything works fine. I have never observed this with
 Grizzly.

  Regards,

 Vikash



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

Re: [Openstack] [Nova] Launch of VM failed after certain count openstack Havana

[Vikash Kumar]

Hi Hrushikesh,

On Tue, Jul 8, 2014 at 10:53 AM, Gangur, Hrushikesh (R  D HP Cloud) 
hrushikesh.gan...@hp.com wrote:

  If it is not going to nova-compute, it must be thrown out directly at
 nova-api due to any of the following reasons:


May be, but even doesn't see nova-api error logs.

  1.   No valid host to launch the instance: Though you can see free
 memory on the compute node, but it does check for few more things: disk
 space and CPU. Please note that the disk space being looked at is the
 theoretical value.

 2.   The instance flavor type is incorrect. The image uploaded might
 have not been specified the right correct min. disk and min. memory needs.
 So, if you use tiny flavor and the image really requires more than 2 GB of
 root, it is going to fail.




I will check with the below command.


  You may like to run the following command:

 nova hypervisor-stats



 Regards~hrushi



 *From:* Vikash Kumar [mailto:vikash.ku...@oneconvergence.com]
 *Sent:* Monday, July 07, 2014 9:13 PM
 *To:* Openstack Milis; openstack-dev
 *Subject:* [Openstack] [Nova] Launch of VM failed after certain count
 openstack Havana



 Hi all,

 I am facing issue with VM launch. I am using openstack *Havana.* I
 have one compute node with following specification:

 root@compute-node:~# lscpu
 Architecture:  x86_64
 CPU op-mode(s):32-bit, 64-bit
 Byte Order:Little Endian
 CPU(s):8
 On-line CPU(s) list:   0-7
 Thread(s) per core:1
 Core(s) per socket:4
 Socket(s): 2
 NUMA node(s):  1
 Vendor ID: GenuineIntel
 CPU family:6
 Model: 15
 Stepping:  7
 CPU MHz:   1995.104
 BogoMIPS:  3990.02
 Virtualization:VT-x
 L1d cache: 32K
 L1i cache: 32K
 L2 cache:  4096K
 NUMA node0 CPU(s): 0-7

 root@compute-node:~# free -h
  total   used   free sharedbuffers cached
 Mem:   15G   1.5G14G 0B   174M   531M
 -/+ buffers/cache:   870M14G
 Swap:  15G 0B15G

  But I am not able to launch more than 12-14 VM. VM launch fails. Even I
 don't see *ERROR *logs in any of nova logs on both *openstack controller
 and compute node.* Don't see any request coming to compute node also. I
 just tailed nova compute logs on compute node. As soon as, I clean the
 previous VMs , everything works fine. I have never observed this with
 Grizzly.

  Regards,

 Vikash



___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[openstack-dev] [Openstack][Nova] Launch of VM failed after certain count openstack Havana

[Vikash Kumar]

Hi all,

I am facing issue with VM launch. I am using openstack *Havana.* I have
one compute node with following specification:

root@compute-node:~# lscpu
Architecture:  x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):8
On-line CPU(s) list:   0-7
Thread(s) per core:1
Core(s) per socket:4
Socket(s): 2
NUMA node(s):  1
Vendor ID: GenuineIntel
CPU family:6
Model: 15
Stepping:  7
CPU MHz:   1995.104
BogoMIPS:  3990.02
Virtualization:VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache:  4096K
NUMA node0 CPU(s): 0-7

root@compute-node:~# free -h
 total   used   free sharedbuffers cached
Mem:   15G   1.5G14G 0B   174M   531M
-/+ buffers/cache:   870M14G
Swap:  15G 0B15G


But I am not able to launch more than 12-14 VM. VM launch fails. Even I
don't see *ERROR *logs in any of nova logs on both *openstack controller
and compute node.* Don't see any request coming to compute node also. I
just tailed nova compute logs on compute node. As soon as, I clean the
previous VMs , everything works fine. I have never observed this with
Grizzly.


Regards,
Vikash
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack][nova][Neutron] Launch VM with multiple Ethernet interfaces with I.P. of single subnet.

[Vikash Kumar]

Hi Racha,

   To answer ur question, by going on to future requirements of service
insertion (especially L2)   we thought that this seems to be one of the
basic requirement and openstack should have it. As u can see in this thread
*Prasad* has pointed one of the detailed use case and we can realize that
use case easily in virtual world. I also agree that there are security
related issues. But at the same time it can be solved also like some other
companies are doing. Anyways it seems for time being, community doesn't see
this as requirement. :)


On Tue, Apr 22, 2014 at 11:06 PM, racha ben...@gmail.com wrote:

 Hi Vikash,
I am wondering why you need to have specs approved to have things
 working as you want? There's nothing that prevent you to have openstack
 support whatever you want except probably for vendor proprietary plugins.
 Install OpenStack with Neutron, search for one of the multi patches that
 enable that in Nova and apply it to your installation, and voila you can
 have nova boot VMs with multi vnics on same neutron. If you want to test
 your setup with a public cloud provider that allow that, you can loock in
 to Amazon EC2.

 Best Regards,
 Racha



 On Wed, Apr 16, 2014 at 3:48 AM, Vikash Kumar 
 vikash.ku...@oneconvergence.com wrote:

 Hi,

  I want to launch one VM which will have two Ethernet interfaces with
 IP of single subnet. Is this supported now in openstack ? Any suggestion ?


 Thanx

 ___
 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] [openstack-dev] [nova][Neutron] Launch VM with multiple Ethernet interfaces with I.P. of single subnet.

[Vikash Kumar]

Hi Racha,

   To answer ur question, by going on to future requirements of service
insertion (especially L2)   we thought that this seems to be one of the
basic requirement and openstack should have it. As u can see in this thread
*Prasad* has pointed one of the detailed use case and we can realize that
use case easily in virtual world. I also agree that there are security
related issues. But at the same time it can be solved also like some other
companies are doing. Anyways it seems for time being, community doesn't see
this as requirement. :)


On Tue, Apr 22, 2014 at 11:06 PM, racha ben...@gmail.com wrote:

 Hi Vikash,
I am wondering why you need to have specs approved to have things
 working as you want? There's nothing that prevent you to have openstack
 support whatever you want except probably for vendor proprietary plugins.
 Install OpenStack with Neutron, search for one of the multi patches that
 enable that in Nova and apply it to your installation, and voila you can
 have nova boot VMs with multi vnics on same neutron. If you want to test
 your setup with a public cloud provider that allow that, you can loock in
 to Amazon EC2.

 Best Regards,
 Racha



 On Wed, Apr 16, 2014 at 3:48 AM, Vikash Kumar 
 vikash.ku...@oneconvergence.com wrote:

 Hi,

  I want to launch one VM which will have two Ethernet interfaces with
 IP of single subnet. Is this supported now in openstack ? Any suggestion ?


 Thanx

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



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


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [Openstack][nova][Neutron] Launch VM with multiple Ethernet interfaces with I.P. of single subnet.

[Vikash Kumar]

*With 'interfaces' I mean 'nics' of VM*.


On Wed, Apr 16, 2014 at 4:18 PM, Vikash Kumar 
vikash.ku...@oneconvergence.com wrote:

 Hi,

  I want to launch one VM which will have two Ethernet interfaces with
 IP of single subnet. Is this supported now in openstack ? Any suggestion ?


 Thanx

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

Re: [openstack-dev] [Openstack][nova][Neutron] Launch VM with multiple Ethernet interfaces with I.P. of single subnet.

[Vikash Kumar]

Aaron,

   One of the use case is to create L2 segments in a network. I can
elaborate this use case if u want.



On Thu, Apr 17, 2014 at 6:20 AM, Aaron Rosen aaronoro...@gmail.com wrote:

 This is true. Several people have asked this same question over the years
 though I've yet to hear a use case why one really need to do this. Do you
 have one?


 On Wed, Apr 16, 2014 at 3:12 PM, Ronak Shah ro...@nuagenetworks.netwrote:

 Hi Vikash,
 Currently this is not supported. the NIC not only needs to be in
 different subnet, they have to be in different network as well (container
 for the subnet)

 Thanks
 Ronak

 On Wed, Apr 16, 2014 at 3:51 AM, Vikash Kumar 
 vikash.ku...@oneconvergence.com wrote:

 *With 'interfaces' I mean 'nics' of VM*.


 On Wed, Apr 16, 2014 at 4:18 PM, Vikash Kumar 
 vikash.ku...@oneconvergence.com wrote:

 Hi,

  I want to launch one VM which will have two Ethernet interfaces
 with IP of single subnet. Is this supported now in openstack ? Any
 suggestion ?


 Thanx



 ___
 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] [Openstack][nova][Neutron] Launch VM with multiple Ethernet interfaces with I.P. of single subnet.

[Vikash Kumar]

Lets say I have source S1 on n/w net1, destination S2 on net1 and i want to
firewall traffic coming from S1 destined to S2. I can use L3 firewall but
in that case the packet headers will have different values, not the same
source and destination. Instead, we can divide network in L2 segments and
steer packets to get the necessary processing. Though I didn't covered the
minute details but hope kept my point. And yes this aliasing thing isn't
the way to solve it.


On Thu, Apr 17, 2014 at 9:23 AM, Kevin Benton blak...@gmail.com wrote:

 Web server running multiple SSL sites that wants to be compatible with
 clients that don't support the SNI extension. There is no way for a server
 to get multiple IP addresses on the same interface is there?


 On Wed, Apr 16, 2014 at 5:50 PM, Aaron Rosen aaronoro...@gmail.comwrote:

 This is true. Several people have asked this same question over the years
 though I've yet to hear a use case why one really need to do this. Do you
 have one?


 On Wed, Apr 16, 2014 at 3:12 PM, Ronak Shah ro...@nuagenetworks.netwrote:

 Hi Vikash,
 Currently this is not supported. the NIC not only needs to be in
 different subnet, they have to be in different network as well (container
 for the subnet)

 Thanks
 Ronak

 On Wed, Apr 16, 2014 at 3:51 AM, Vikash Kumar 
 vikash.ku...@oneconvergence.com wrote:

 *With 'interfaces' I mean 'nics' of VM*.


 On Wed, Apr 16, 2014 at 4:18 PM, Vikash Kumar 
 vikash.ku...@oneconvergence.com wrote:

 Hi,

  I want to launch one VM which will have two Ethernet interfaces
 with IP of single subnet. Is this supported now in openstack ? Any
 suggestion ?


 Thanx



 ___
 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




 --
 Kevin Benton

 ___
 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] [Openstack][nova][Neutron] Launch VM with multiple Ethernet interfaces with I.P. of single subnet.

[Vikash Kumar]

Kevin , this can be one approach but not sure. But certainly won't solve
all cases. :)




On Thu, Apr 17, 2014 at 10:33 AM, Kevin Benton blak...@gmail.com wrote:

 Yeah, I was aware of allowed address pairs, but that doesn't help with the
 IP allocation part.

 Is this the tenant workflow for this use case?

 1. Create an instance.
 2. Wait to see what which subnet it gets an allocation from.
 3. Pick an IP from that subnet that doesn't currently appear to be in use.
 4. Use the neutron-cli or API to update the port object with the extra IP.
 5. Hope that Neutron will never allocate that IP address for something
 else.


 On Wed, Apr 16, 2014 at 9:46 PM, Aaron Rosen aaronoro...@gmail.comwrote:

 Whoops Akihiro beat me to it :)


 On Wed, Apr 16, 2014 at 9:46 PM, Aaron Rosen aaronoro...@gmail.comwrote:

 The allowed-address-pair extension that was added here (
 https://review.openstack.org/#/c/38230/) allows us to add arbitrary ips
 to an interface to allow them. This is useful if you want to run something
 like VRRP between two instances.


 On Wed, Apr 16, 2014 at 9:39 PM, Kevin Benton blak...@gmail.com wrote:

 I was under the impression that the security group rules blocked
 addresses not assigned by neutron[1].

 1.
 https://github.com/openstack/neutron/blob/master/neutron/agent/linux/iptables_firewall.py#L188


 On Wed, Apr 16, 2014 at 9:20 PM, Aaron Rosen aaronoro...@gmail.comwrote:

 You can do it with ip aliasing and use one interface:

 ifconfig eth0 10.0.0.22/24
 ifconfig eth0:1 10.0.0.23/24
 ifconfig eth0:2 10.0.0.24/24

 2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc mq state
 DOWN qlen 1000
 link/ether 40:6c:8f:1a:a9:31 brd ff:ff:ff:ff:ff:ff
 inet 10.0.0.22/24 brd 10.0.0.255 scope global eth0
valid_lft forever preferred_lft forever
 inet 10.0.0.23/24 brd 10.0.0.255 scope global secondary eth0:1
valid_lft forever preferred_lft forever
 inet 10.0.0.24/24 brd 10.0.0.255 scope global secondary eth0:2
valid_lft forever preferred_lft forever



 On Wed, Apr 16, 2014 at 8:53 PM, Kevin Benton blak...@gmail.comwrote:

 Web server running multiple SSL sites that wants to be compatible
 with clients that don't support the SNI extension. There is no way for a
 server to get multiple IP addresses on the same interface is there?


 On Wed, Apr 16, 2014 at 5:50 PM, Aaron Rosen 
 aaronoro...@gmail.comwrote:

 This is true. Several people have asked this same question over the
 years though I've yet to hear a use case why one really need to do 
 this. Do
 you have one?


 On Wed, Apr 16, 2014 at 3:12 PM, Ronak Shah ro...@nuagenetworks.net
  wrote:

 Hi Vikash,
 Currently this is not supported. the NIC not only needs to be in
 different subnet, they have to be in different network as well 
 (container
 for the subnet)

 Thanks
 Ronak

 On Wed, Apr 16, 2014 at 3:51 AM, Vikash Kumar 
 vikash.ku...@oneconvergence.com wrote:

 *With 'interfaces' I mean 'nics' of VM*.


 On Wed, Apr 16, 2014 at 4:18 PM, Vikash Kumar 
 vikash.ku...@oneconvergence.com wrote:

 Hi,

  I want to launch one VM which will have two Ethernet
 interfaces with IP of single subnet. Is this supported now in 
 openstack ?
 Any suggestion ?


 Thanx



 ___
 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




 --
 Kevin Benton

 ___
 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




 --
 Kevin Benton

 ___
 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




 --
 Kevin Benton

 ___
 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] [Openstack][nova][Neutron] Launch VM with multiple Ethernet interfaces with I.P. of single subnet.

[Vikash Kumar]

Aaron,

  The idea is to steer packets coming from source S1 ( belong to net1)
destined to destination D1 (belong to net1)  through bunch of L2 appliances
(like firewall) without modifying packet headers. The core idea is to keep
appliances (on net1), source S1 (VM on net1) and destination D1(VM on
net1)  on same broadcast domain. I hope it wl now make sense.


On Thu, Apr 17, 2014 at 10:47 AM, Vikash Kumar 
vikash.ku...@oneconvergence.com wrote:

 Kevin , this can be one approach but not sure. But certainly won't solve
 all cases. :)




 On Thu, Apr 17, 2014 at 10:33 AM, Kevin Benton blak...@gmail.com wrote:

 Yeah, I was aware of allowed address pairs, but that doesn't help with
 the IP allocation part.

 Is this the tenant workflow for this use case?

 1. Create an instance.
 2. Wait to see what which subnet it gets an allocation from.
 3. Pick an IP from that subnet that doesn't currently appear to be in use.
 4. Use the neutron-cli or API to update the port object with the extra IP.
 5. Hope that Neutron will never allocate that IP address for something
 else.


 On Wed, Apr 16, 2014 at 9:46 PM, Aaron Rosen aaronoro...@gmail.comwrote:

 Whoops Akihiro beat me to it :)


 On Wed, Apr 16, 2014 at 9:46 PM, Aaron Rosen aaronoro...@gmail.comwrote:

 The allowed-address-pair extension that was added here (
 https://review.openstack.org/#/c/38230/) allows us to add arbitrary
 ips to an interface to allow them. This is useful if you want to run
 something like VRRP between two instances.


 On Wed, Apr 16, 2014 at 9:39 PM, Kevin Benton blak...@gmail.comwrote:

 I was under the impression that the security group rules blocked
 addresses not assigned by neutron[1].

 1.
 https://github.com/openstack/neutron/blob/master/neutron/agent/linux/iptables_firewall.py#L188


 On Wed, Apr 16, 2014 at 9:20 PM, Aaron Rosen aaronoro...@gmail.comwrote:

 You can do it with ip aliasing and use one interface:

 ifconfig eth0 10.0.0.22/24
 ifconfig eth0:1 10.0.0.23/24
 ifconfig eth0:2 10.0.0.24/24

 2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc mq state
 DOWN qlen 1000
 link/ether 40:6c:8f:1a:a9:31 brd ff:ff:ff:ff:ff:ff
 inet 10.0.0.22/24 brd 10.0.0.255 scope global eth0
valid_lft forever preferred_lft forever
 inet 10.0.0.23/24 brd 10.0.0.255 scope global secondary eth0:1
valid_lft forever preferred_lft forever
 inet 10.0.0.24/24 brd 10.0.0.255 scope global secondary eth0:2
valid_lft forever preferred_lft forever



 On Wed, Apr 16, 2014 at 8:53 PM, Kevin Benton blak...@gmail.comwrote:

 Web server running multiple SSL sites that wants to be compatible
 with clients that don't support the SNI extension. There is no way for a
 server to get multiple IP addresses on the same interface is there?


 On Wed, Apr 16, 2014 at 5:50 PM, Aaron Rosen 
 aaronoro...@gmail.comwrote:

 This is true. Several people have asked this same question over the
 years though I've yet to hear a use case why one really need to do 
 this. Do
 you have one?


 On Wed, Apr 16, 2014 at 3:12 PM, Ronak Shah 
 ro...@nuagenetworks.net wrote:

 Hi Vikash,
 Currently this is not supported. the NIC not only needs to be in
 different subnet, they have to be in different network as well 
 (container
 for the subnet)

 Thanks
 Ronak

 On Wed, Apr 16, 2014 at 3:51 AM, Vikash Kumar 
 vikash.ku...@oneconvergence.com wrote:

 *With 'interfaces' I mean 'nics' of VM*.


 On Wed, Apr 16, 2014 at 4:18 PM, Vikash Kumar 
 vikash.ku...@oneconvergence.com wrote:

 Hi,

  I want to launch one VM which will have two Ethernet
 interfaces with IP of single subnet. Is this supported now in 
 openstack ?
 Any suggestion ?


 Thanx



 ___
 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




 --
 Kevin Benton

 ___
 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




 --
 Kevin Benton

 ___
 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] [openstack-dev][nova][Neutron] Launch VM with multiple Ethernet interfaces with I.P. of single subnet.

[Vikash Kumar]

Hi,

 I want to launch one VM which will have two Ethernet interfaces with
IP of single subnet. Is this supported now in openstack ? Any suggestion ?


Thanx
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack-dev][nova][Neutron] Launch VM with multiple Ethernet interfaces with I.P. of single subnet.

[Vikash Kumar]

*With 'interfaces' I mean 'nics' of VM*.


On Wed, Apr 16, 2014 at 4:18 PM, Vikash Kumar 
vikash.ku...@oneconvergence.com wrote:

 Hi,

  I want to launch one VM which will have two Ethernet interfaces with
 IP of single subnet. Is this supported now in openstack ? Any suggestion ?


 Thanx

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Dnsmasq process not running

[Vikash Kumar]

Hi all,

I have installed openstack grizzly. My VM's were not getting IP. I
checked my netork node and found that dnsmasq process is not running. Tried
restarting quantum-dhcp-agent but none of the time dnsmasq process came up.


How can I solve this problem ?


Thanks
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Dnsmasq process not running

[Vikash Kumar]

Guys , thnx for reply. I got the cause of problem. Actually dnsmasq process
was not installed properly.


On Thu, Feb 13, 2014 at 8:20 PM, Remo Mattei r...@italy1.com wrote:

 Did you install it from devstack? Packstack ? Os? You are missing a lot of
 info very hard to get help.

 Inviato da iPhone ()

  Il giorno Feb 13, 2014, alle ore 6:18, Vikash Kumar 
 vikash.ku...@oneconvergence.com ha scritto:
 
  Hi all,
 
  I have installed openstack grizzly. My VM's were not getting IP. I
 checked my netork node and found that dnsmasq process is not running. Tried
 restarting quantum-dhcp-agent but none of the time dnsmasq process came up.
 
 
  How can I solve this problem ?
 
 
  Thanks
  !DSPAM:1,52fcd7f0306121429015326!
  ___
  Mailing list:
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
  Post to : openstack@lists.openstack.org
  Unsubscribe :
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
 
 
  !DSPAM:1,52fcd7f0306121429015326!

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] dhcp request can't reach br-int of network node

[Vikash Kumar]

U can try few things quickly.

a) Connectivity between ur compute node and n/w node. Check the interfaces.
b) Check the route entry.

Ur compute node can ping to n/w node. U can also chk the vlan tag settings
on ovs bridge.


On Fri, Feb 7, 2014 at 10:11 PM, Chris Baker openstack2...@qq.com wrote:

 Hi guys,

 My havana installation has 3 nodes:
 control node, runs keystone APIs and neutron server;
 network node, runs l3, dhcp, metadata, ovs agents; with VLAN mode
 compute node, runs nova compute and ovs agents;

 repo from http://repos.fedorapeople.org/repos/openstack/openstack-havana,
 and the os gets updated well with latest kernel.


 Currently my VM can't get dhcp ack from network node.
 Based the topology picture for the package flow:
 http://docs.openstack.org/admin-guide-cloud/content/figures/10/a/common/
 figures/under-the-hood-scenario-1-ovs-network.png

 With the tcpdump result on both network and compute node, it says the dhcp
 request successfully leaves compute node, and it can reach the
 int-br-eth1 of network node, but not the next step br br-int, so the
 dnsmasq would not able to ack. I think this is the problem why I can't get
 dhcp ipaddr.

 # uname -r
 2.6.32-358.123.2.openstack.el6.x86_64

 # ip netns  (should we say namespace works well?)
 qdhcp-11f3adc1-6a2e-429b-9679-b565347e2f74
 qdhcp-4aaa7c19-7864-4b17-aebc-d6aa354d4cd5
 qdhcp-285e259e-e3ec-4149-81db-8e94e1713aa2
 qdhcp-4044cdf0-717b-4628-9ce0-a9ff49533d8f
 qrouter-76c9b884-5928-42f4-a016-afab1b72066b

 Anyone can help where/which section I should check for the issue next? or
 let me know if other info is needed.
 Thanks a lot.

 Chris

 ___
 Mailing list:
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
 Post to : openstack@lists.openstack.org
 Unsubscribe :
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] dhcp request can't reach br-int of network node

[Vikash Kumar]

Chen ,

I think ur packets is getting dropped. U can verify this by just
checking the packets coming from compute node hitting which of the rules in
br-int.


On Wed, Feb 12, 2014 at 10:56 AM, Robert Collins
robe...@robertcollins.netwrote:

 Check the outbound ofctl rules on your hypervisor nodes. If they
 aren't tagging traffic properly, it won't be processed by the incoming
 gre rules and you'll see the symptoms you have.

 On 8 February 2014 05:41, Chris Baker openstack2...@qq.com wrote:
  Hi guys,
 
  My havana installation has 3 nodes:
  control node, runs keystone APIs and neutron server;
  network node, runs l3, dhcp, metadata, ovs agents; with VLAN mode
  compute node, runs nova compute and ovs agents;
 
  repo from http://repos.fedorapeople.org/repos/openstack/openstack-havana
 ,
  and the os gets updated well with latest kernel.
 
 
  Currently my VM can't get dhcp ack from network node.
  Based the topology picture for the package flow:
 
 http://docs.openstack.org/admin-guide-cloud/content/figures/10/a/common/figures/under-the-hood-scenario-1-ovs-network.png
 
  With the tcpdump result on both network and compute node, it says the
 dhcp
  request successfully leaves compute node, and it can reach the
 int-br-eth1
  of network node, but not the next step br br-int, so the dnsmasq would
 not
  able to ack. I think this is the problem why I can't get dhcp ipaddr.
 
  # uname -r
  2.6.32-358.123.2.openstack.el6.x86_64
 
  # ip netns  (should we say namespace works well?)
  qdhcp-11f3adc1-6a2e-429b-9679-b565347e2f74
  qdhcp-4aaa7c19-7864-4b17-aebc-d6aa354d4cd5
  qdhcp-285e259e-e3ec-4149-81db-8e94e1713aa2
  qdhcp-4044cdf0-717b-4628-9ce0-a9ff49533d8f
  qrouter-76c9b884-5928-42f4-a016-afab1b72066b
 
  Anyone can help where/which section I should check for the issue next? or
  let me know if other info is needed.
  Thanks a lot.
 
  Chris
 
  ___
  Mailing list:
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
  Post to : openstack@lists.openstack.org
  Unsubscribe :
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
 



 --
 Robert Collins rbtcoll...@hp.com
 Distinguished Technologist
 HP Converged Cloud

 ___
 Mailing list:
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
 Post to : openstack@lists.openstack.org
 Unsubscribe :
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] What to check when vm not get IP

[Vikash Kumar]

First step, do dhclient on the interface of vm and then do tcpdump on dhcp
namespace interface. U wl get a clue.


On Tue, Dec 10, 2013 at 1:49 PM, Mahardhika Gilang 
mahardika.gil...@andalabs.com wrote:

 Hi all,

 This question seems like repeat from another question. But i will ask to
 make it clear.
 What component to check if vm not get local ip that we define in neutron?
 i have check dhcp_agent and it just look fine, And i have tried put the IP
 manual into vm to ping router gateway local, and its not get any reply.
 what should i check? This happen when i upgrade from grizzly to havana.

 Thanks
 --
 Regards,
 Mahardhika Gilang



 ___
 Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
 openstack
 Post to : openstack@lists.openstack.org
 Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
 openstack

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[openstack-dev] [Nova] VNC issue with multi compute node with openstack havana

[Vikash Kumar]

Hi,

  I used devstack Multi-Node + VLANs to install openstack-havana recently.
Installation was successful and i verified basic things like vm launch,
ping between vm's.

  I have two nodes: 1. Ctrl+Compute  2. Compute

  The VM which gets launched on second compute node (here 2, see above)
doesn't gets vnc console. I tried to acces from both horizon and the url
given by nova-cli.

   The *n-novnc* screen on first node which is controller (here 1) gave
this error log:

   Traceback (most recent call last):
  File /usr/local/lib/python2.7/dist-packages/websockify/websocket.py,
line 711, in top_new_client
self.new_client()
  File /opt/stack/nova/nova/console/websocketproxy.py, line 68, in
new_client
tsock = self.socket(host, port, connect=True)
  File /usr/local/lib/python2.7/dist-packages/websockify/websocket.py,
line 188, in socket
sock.connect(addrs[0][4])
  File /usr/local/lib/python2.7/dist-packages/eventlet/greenio.py, line
192, in connect
socket_checkerr(fd)
  File /usr/local/lib/python2.7/dist-packages/eventlet/greenio.py, line
46, in socket_checkerr
raise socket.error(err, errno.errorcode[err])
error: [Errno 111] ECONNREFUSED


  The vnc related configuration in nova.conf on Ctrl+Compute node:

   vncserver_proxyclient_address = 127.0.0.1
   vncserver_listen = 127.0.0.1
   vnc_enabled = true
   xvpvncproxy_base_url = http://192.168.2.151:6081/console
   novncproxy_base_url = http://192.168.2.151:6080/vnc_auto.html

   and on second Compute node:
  /* I corrected the I.P. of first two address, by default it sets to
127.0.0.1 */
   vncserver_proxyclient_address = 192.168.2.157
   vncserver_listen = 0.0.0.0
   vnc_enabled = true
   xvpvncproxy_base_url = http://192.168.2.151:6081/console
   novncproxy_base_url = http://192.168.2.151:6080/vnc_auto.html

I also added the host name of compute node in hosts file of
controllernode. With this ERORR 111 gone and new error came.

connecting to: 192.168.2.157:-1
  7: handler exception: [Errno -8] Servname not supported for ai_socktype
  7: Traceback (most recent call last):
  File /usr/local/lib/python2.7/dist-packages/websockify/websocket.py,
line 711, in top_new_client
self.new_client()
  File /opt/stack/nova/nova/console/websocketproxy.py, line 68, in
new_client
tsock = self.socket(host, port, connect=True)
  File /usr/local/lib/python2.7/dist-packages/websockify/websocket.py,
line 180, in socket
socket.IPPROTO_TCP, flags)
  gaierror: [Errno -8] Servname not supported for ai_socktype


   What need to be done to resolve this ?

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

[Openstack] VNC issue with multi compute node with openstack havana

[Vikash Kumar]

Hi,

  I used devstack Multi-Node + VLANs to install openstack-havana recently.
Installation was successful and i verified basic things like vm launch,
ping between vm's.

  I have two nodes: 1. Ctrl+Compute  2. Compute

  The VM which gets launched on second compute node (here 2, see above)
doesn't gets vnc console. I tried to acces from both horizon and the url
given by nova-cli.

   The *n-novnc* screen on first node which is controller (here 1) gave
this error log:

   Traceback (most recent call last):
  File /usr/local/lib/python2.7/dist-packages/websockify/websocket.py,
line 711, in top_new_client
self.new_client()
  File /opt/stack/nova/nova/console/websocketproxy.py, line 68, in
new_client
tsock = self.socket(host, port, connect=True)
  File /usr/local/lib/python2.7/dist-packages/websockify/websocket.py,
line 188, in socket
sock.connect(addrs[0][4])
  File /usr/local/lib/python2.7/dist-packages/eventlet/greenio.py, line
192, in connect
socket_checkerr(fd)
  File /usr/local/lib/python2.7/dist-packages/eventlet/greenio.py, line
46, in socket_checkerr
raise socket.error(err, errno.errorcode[err])
error: [Errno 111] ECONNREFUSED


  The vnc related configuration in nova.conf on Ctrl+Compute node:

   vncserver_proxyclient_address = 127.0.0.1
   vncserver_listen = 127.0.0.1
   vnc_enabled = true
   xvpvncproxy_base_url = http://192.168.2.151:6081/console
   novncproxy_base_url = http://192.168.2.151:6080/vnc_auto.html

   and on second Compute node:
  /* I corrected the I.P. of first two address, by default it sets to
127.0.0.1 */
   vncserver_proxyclient_address = 192.168.2.157
   vncserver_listen = 0.0.0.0
   vnc_enabled = true
   xvpvncproxy_base_url = http://192.168.2.151:6081/console
   novncproxy_base_url = http://192.168.2.151:6080/vnc_auto.html

I also added the host name of compute node in hosts file of
controllernode. With this ERORR 111 gone and new error came.

connecting to: 192.168.2.157:-1
  7: handler exception: [Errno -8] Servname not supported for ai_socktype
  7: Traceback (most recent call last):
  File /usr/local/lib/python2.7/dist-packages/websockify/websocket.py,
line 711, in top_new_client
self.new_client()
  File /opt/stack/nova/nova/console/websocketproxy.py, line 68, in
new_client
tsock = self.socket(host, port, connect=True)
  File /usr/local/lib/python2.7/dist-packages/websockify/websocket.py,
line 180, in socket
socket.IPPROTO_TCP, flags)
  gaierror: [Errno -8] Servname not supported for ai_socktype


   What need to be done to resolve this ?

Thnx
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[openstack-dev] [devstack] Openstack Multinode installation with Devstack

[Vikash Kumar]

Hi everyone,

Did anyone have tried openstack installation with Devstack recently ?
Particularly, *Multi node installation* and with the recent code in
openstack-dev git.

Is the devstack code is ready to install latest Havana ?

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

[openstack-dev] Issue with MutliNode openstack installation with devstack

[Vikash Kumar]

Hi,

   I am trying to install openstack on mutli node with help of devstack (
http://devstack.org/guides/multinode-lab.html).

   I got some issues:

My setup details: One controller and One compute node (both VM).
  OS - Ubuntu 13.04
   Memory: 2G
   *a. VM's are going in paused state.*

   I tried to launch VM from horizon, and all the VM's goes in*
Paused *state.
VM's are scheduled on *compute node.  *

   When controller node come up, *nova-manage service list* shows the
controller node as VM also. Reason by default nova compute services also
come up.

After compute node installation, *nova-manage service list *shows
compute node as compute node only and not the

   There is one nova -error:

   * ERROR nova.openstack.common.periodic_task [-] Error during
ComputeManager.update_available_resource: Compute host oc-vm could not be
found.#012Traceback (most recent call last):#012#012  File
/opt/stack/nova/nova/openstack/common/rpc/common.py, line 420, in
catch_client_exception#012return func(*args, **kwargs)#012#012  File
/opt/stack/nova/nova/conductor/manager.py, line 419, in
service_get_all_by#012result =
self.db.service_get_by_compute_host(context, host)#012#012  File
/opt/stack/nova/nova/db/api.py, line 140, in
service_get_by_compute_host#012return
IMPL.service_get_by_compute_host(context, host)#012#012  File
/opt/stack/nova/nova/db/sqlalchemy/api.py, line 107, in wrapper#012
return f(*args, **kwargs)#012#012  File
/opt/stack/nova/nova/db/sqlalchemy/api.py, line 441, in
service_get_by_compute_host#012raise
exception.ComputeHostNotFound(host=host)#012#012ComputeHostNotFound:
Compute host oc-vm could not be found.#0122013-10-16 06:25:27.358 7143
TRACE nova.openstack.common.periodic_task Traceback (most recent call
last):#0122013-10-16 06:25:27.358 7143 TRACE
nova.openstack.common.periodic_task   File
/opt/stack/nova/nova/openstack/common/periodic_task.py, line 180, in
run_periodic_tasks#0122013-10-16 06:25:27.358 7143 TRACE
nova.openstack.common.periodic_task task(self, context)#0122013-10-16
06:25:27.358 7143 TRACE nova.openstack.common.periodic_task   File
/opt/stack/nova/nova/compute/manager.py, line 4872, in
update_available_resource#0122013-10-16 06:25:27.358 7143 TRACE
nova.openstack.common.periodic_task compute_nodes_in_db =
self._get_compute_nodes_in_db(context)#0122013-10-16 06:25:27.358 7143
TRACE nova.openstack.common.periodic_task   File
/opt/stack/nova/nova/compute/manager.py, line 4883, in
_get_compute_nodes_in_db#0122013-10-16 06:25:27.358 7143 TRACE
nova.openstack.common.periodic_task context, self.host)#0122013-10-16
06:25:27.358 7143 TRACE nova.openstack.common.periodic_task   File
/opt/stack/nova/nova/condu*

  * b. g-api was flagging issue. *

*ERROR glance.store.sheepdog [-] Error in store configuration:
Unexpected error while running command.#012Command: collie#012Exit code:
127#012Stdout: ''#012Stderr: '/bin/sh: 1: collie: not found\n'

WARNING glance.store.base [-] Failed to configure store correctly:
Store sheepdog could not be configured correctly. Reason: Error in store
configuration: Unexpected error while running command.#012Command:
collie#012Exit code: 127#012Stdout: ''#012Stderr: '/bin/sh: 1: collie: not
found\n' Disabling add method.

WARNING glance.store.base [-] Failed to configure store correctly:
Store cinder could not be configured correctly. Reason: Cinder storage
requires a context. Disabling add method
*
I think this is a bug and also reported by other developers. I resolved
it by installing *sheepdog *explicitly on compute node. After installation
, i didn't saw that error.


 *My localrc file:

*
* Controller:*
ADMIN_PASSWORD=secret
MYSQL_PASSWORD=secret
RABBIT_PASSWORD=secret
SERVICE_PASSWORD=secret
SERVICE_TOKEN=secret
HOST_IP=192.168.0.66
FLAT_INTERFACE=eth0
FIXED_RANGE=10.0.0.0/24
FIXED_NETWORK_SIZE=128
FLOATING_RANGE=192.168.0.22/24
MULTI_HOST=1
Q_PLUGIN=openvswitch
ENABLE_TENANT_TUNNELS=True
disable_service n-net
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-meta
enable_service neutron
enable_service q-lbaas
DEST=/opt/stack
LOGFILE=stack.sh.log
RECLONE=yes
SCREEN_LOGDIR=/opt/stack/logs/screen
SYSLOG=True

**I have enabled GRE tunneling.*

  *Compute Node:*

ADMIN_PASSWORD=secret
MYSQL_PASSWORD=secret
RABBIT_PASSWORD=secret
SERVICE_PASSWORD=secret
SERVICE_TOKEN=secret
HOST_IP=192.168.0.103
FLAT_INTERFACE=eth0
FIXED_RANGE=10.0.0.0/24
FIXED_NETWORK_SIZE=128
FLOATING_RANGE=192.168.0.22/24
MULTI_HOST=1
DATABASE_TYPE=mysql
SERVICE_HOST=192.168.0.66
MYSQL_HOST=192.168.0.66
RABBIT_HOST=192.168.0.66
GLANCE_HOSTPORT=192.168.0.66:9292
Q_HOST=192.168.0.66
MATCHMAKER_REDIS_HOST=192.168.0.66
ENABLE_TENANT_TUNNELS=True
disable_service n-net
enable_service n-cpu rabbit q-agt neutron
Q_PLUGIN=openvswitch
DEST=/opt/stack
LOGFILE=stack.sh.log
RECLONE=yes

[openstack-dev] [nova] [devstack] Re: Issue with MutliNode openstack installation with devstack

[Vikash Kumar]

On Wed, Oct 16, 2013 at 8:15 PM, Vikash Kumar 
vikash.ku...@oneconvergence.com wrote:

 Hi,

I am trying to install openstack on mutli node with help of devstack (
 http://devstack.org/guides/multinode-lab.html).

I got some issues:

 My setup details: One controller and One compute node (both VM).
   OS - Ubuntu 13.04
Memory: 2G
*a. VM's are going in paused state.*

I tried to launch VM from horizon, and all the VM's goes in*Paused
 *state. VM's are scheduled on *compute node.  *

When controller node come up, *nova-manage service list* shows the
 controller node as VM also. Reason by default nova compute services also
 come up.

 After compute node installation, *nova-manage service list *shows
 compute node as compute node only and not the

There is one nova -error:

* ERROR nova.openstack.common.periodic_task [-] Error during
 ComputeManager.update_available_resource: Compute host oc-vm could not be
 found.#012Traceback (most recent call last):#012#012  File
 /opt/stack/nova/nova/openstack/common/rpc/common.py, line 420, in
 catch_client_exception#012return func(*args, **kwargs)#012#012  File
 /opt/stack/nova/nova/conductor/manager.py, line 419, in
 service_get_all_by#012result =
 self.db.service_get_by_compute_host(context, host)#012#012  File
 /opt/stack/nova/nova/db/api.py, line 140, in
 service_get_by_compute_host#012return
 IMPL.service_get_by_compute_host(context, host)#012#012  File
 /opt/stack/nova/nova/db/sqlalchemy/api.py, line 107, in wrapper#012
 return f(*args, **kwargs)#012#012  File
 /opt/stack/nova/nova/db/sqlalchemy/api.py, line 441, in
 service_get_by_compute_host#012raise
 exception.ComputeHostNotFound(host=host)#012#012ComputeHostNotFound:
 Compute host oc-vm could not be found.#0122013-10-16 06:25:27.358 7143
 TRACE nova.openstack.common.periodic_task Traceback (most recent call
 last):#0122013-10-16 06:25:27.358 7143 TRACE
 nova.openstack.common.periodic_task   File
 /opt/stack/nova/nova/openstack/common/periodic_task.py, line 180, in
 run_periodic_tasks#0122013-10-16 06:25:27.358 7143 TRACE
 nova.openstack.common.periodic_task task(self, context)#0122013-10-16
 06:25:27.358 7143 TRACE nova.openstack.common.periodic_task   File
 /opt/stack/nova/nova/compute/manager.py, line 4872, in
 update_available_resource#0122013-10-16 06:25:27.358 7143 TRACE
 nova.openstack.common.periodic_task compute_nodes_in_db =
 self._get_compute_nodes_in_db(context)#0122013-10-16 06:25:27.358 7143
 TRACE nova.openstack.common.periodic_task   File
 /opt/stack/nova/nova/compute/manager.py, line 4883, in
 _get_compute_nodes_in_db#0122013-10-16 06:25:27.358 7143 TRACE
 nova.openstack.common.periodic_task context, self.host)#0122013-10-16
 06:25:27.358 7143 TRACE nova.openstack.common.periodic_task   File
 /opt/stack/nova/nova/condu*

   * b. g-api was flagging issue. *

 *ERROR glance.store.sheepdog [-] Error in store configuration:
 Unexpected error while running command.#012Command: collie#012Exit code:
 127#012Stdout: ''#012Stderr: '/bin/sh: 1: collie: not found\n'

 WARNING glance.store.base [-] Failed to configure store correctly:
 Store sheepdog could not be configured correctly. Reason: Error in store
 configuration: Unexpected error while running command.#012Command:
 collie#012Exit code: 127#012Stdout: ''#012Stderr: '/bin/sh: 1: collie: not
 found\n' Disabling add method.

 WARNING glance.store.base [-] Failed to configure store correctly:
 Store cinder could not be configured correctly. Reason: Cinder storage
 requires a context. Disabling add method
 *
 I think this is a bug and also reported by other developers. I
 resolved it by installing *sheepdog *explicitly on compute node. After
 installation , i didn't saw that error.


  *My localrc file:

 *
 * Controller:*
 ADMIN_PASSWORD=secret
 MYSQL_PASSWORD=secret
 RABBIT_PASSWORD=secret
 SERVICE_PASSWORD=secret
 SERVICE_TOKEN=secret
 HOST_IP=192.168.0.66
 FLAT_INTERFACE=eth0
 FIXED_RANGE=10.0.0.0/24
 FIXED_NETWORK_SIZE=128
 FLOATING_RANGE=192.168.0.22/24
 MULTI_HOST=1
 Q_PLUGIN=openvswitch
 ENABLE_TENANT_TUNNELS=True
 disable_service n-net
 enable_service q-svc
 enable_service q-agt
 enable_service q-dhcp
 enable_service q-l3
 enable_service q-meta
 enable_service neutron
 enable_service q-lbaas
 DEST=/opt/stack
 LOGFILE=stack.sh.log
 RECLONE=yes
 SCREEN_LOGDIR=/opt/stack/logs/screen
 SYSLOG=True

 **I have enabled GRE tunneling.*

   *Compute Node:*

 ADMIN_PASSWORD=secret
 MYSQL_PASSWORD=secret
 RABBIT_PASSWORD=secret
 SERVICE_PASSWORD=secret
 SERVICE_TOKEN=secret
 HOST_IP=192.168.0.103
 FLAT_INTERFACE=eth0
 FIXED_RANGE=10.0.0.0/24
 FIXED_NETWORK_SIZE=128
 FLOATING_RANGE=192.168.0.22/24
 MULTI_HOST=1
 DATABASE_TYPE=mysql
 SERVICE_HOST=192.168.0.66
 MYSQL_HOST=192.168.0.66
 RABBIT_HOST=192.168.0.66
 GLANCE_HOSTPORT=192.168.0.66:9292
 Q_HOST=192.168.0.66