Hi Jake,
here's the localrc I tipycally use when I develop for Neutron with the OVS
plugin:
ENABLED_SERVICES=horizon,g-api,g-reg,key,n-api,n-sch,mysql,rabbit,quantum,q-svc,n-cpu,n-cond,cinder,n-crt,q-agt,q-l3,q-dhcp,q-meta
ADMIN_PASSWORD=password
MYSQL_PASSWORD=password
RABBIT_PASSWORD=password
S
On 29 July 2013 18:48, Jarret Raim wrote:
> Two quick questions.
>
>
> When you sign up to present presentations at the summit, you enter your
> name and email address. You never enter a password, but to log back in to a
> pre-existing account, you need a password. Attempting a password reset j
Hi Jake,
most of the info here have been shamelessly copied from
http://devstack.org/guides/single-machine.html
In general devstack.org has plenty of information to understand how it
deploys openstack and troubleshoot issues.
Salvatore
On 31 July 2013 08:59, Jake G. wrote:
> Could someone ple
Hi Ben,
The closest the thing to what you want to achieve is the Floating IP, but,
as you say, this will not allow for fine-grained control over ports; so you
won't be able, for instance, to expose only port 443 of an internal IP.
However, this is not in the Havana roadmap at the moment - but thi
While I'm not in a position to comment for nova-network, at the moment I
can just confirm that Neutron does not support IPv6 L3 forwarding.
However, from what I read from the admin guide (and the code) it should be
ok to specify IPv6 addresses in security group rules.
IPv6 address management, and
As Ashok said, Aaron is working on a patch for removing the need for
holding an IP.
This will make IP addresses immediately reusable, thus removing the 'hold'
process.
This is however not likely to be backported to grizzly; it will be an
havana feature.
Salvatore
On 7 August 2013 17:44, Ashok K
It sounds like you're having an issue with namespaces, I am not sure how
the emer-reset command can help.
Have you tried it and solved your issue for you?
Have you also tried cleaning up your ns state with neutron-netns-cleanup,
which you can run also with the --force option?
Regards,
Salvatore
That is correct - the blueprint that would add this feature is the one
linked by Cristian.
however, please note that now this blueprint has been untargeted from
Havana and it has no assignee.
Salvatore
On 19 August 2013 14:46, Cristian Falcas wrote:
> Can't be done yet with quantum, from what
Hi Alan,
Design session proposal has opened today at summit.openstack.org; on the
other hand conference session proposal closed on July 31st.
I believe voting closed at some point last week (possibly August 29th).
Accepted talks should be announced in a few days. The voting system was
available at
Please add your logs under bug1211915.
It will also helpful to provide client-side debug output: neutron -v
agent-list
Regards,
Salvatore
On 12 October 2013 18:23, Sushma Korati wrote:
> Hi Li,
>
> I am not sure how to clear connection pool but even we faced a similar
> issued because rabiitm
What about your l3 agents?
Please check if you're being hit by this upgrade bug:
https://bugs.launchpad.net/neutron/+bug/1236439
The bug mentions the l3 agents but applies to all agents.
Regards,
Salvatore
On 16 October 2013 20:27, Martinx - ジェームズ wrote:
> Aaron,
>
> I hit that problem again,
>From this traceback the only thing I can think of is that this behaviour is
related to https://bugs.launchpad.net/neutron/+bug/1236439
Can you please check the status of your agents?
Regards,
Salvatore
On 20 October 2013 08:31, Chu Duc Minh wrote:
> I'm upgrading from Grizzly to Havana.
> Aft
Hi Alejandro,
As we've already discussed the topic over IRC, let me add something else on
your setup:
- no dhcp agent, no l3 agent
- IP configuration injected into instances
(I'm disclosing this information since it's already been disclosed on IRC
whose logs are publicly accessible anyway)
Commen
Hi Andre,
Some replies inline, hopefully they might be helpful.
>From my perspective your setup is not that different from the 'classical'
in which controller and network node are separated.
Salvatore
On 18 November 2013 20:17, Andre Charbonneau <
andre.charbonn...@ssc-spc.gc.ca> wrote:
> Hi,
>
Hi Lorin,
I think yours is a very good question; I am afraid I am not able to provide
a straight answer regarding in which cases one service should be preferred
to the other.
Technically the difference would be that a firewall rule is enforced only
at the edge of your network, and is therefore not
This feature will be available in neutron for the Icehouse release, and
will cause a floating IP to be created everytime a VM is booted.
However, it is unlikely that feature will be backported.
For Havana users, the best workaround so far, in my opinion, is:
1) create a port on a subnet connected
Hi and apologies for the delay in the reply.
The neutron API operations define "logical entries", which pretty much
means they just exist in the database.
The database provides agents information concerning how to wire these port.
If you look at the OVS/ML2 plugins, what does the 'magic' for nova
Hi Robert,
I can only confirm that no plugin beyond the one you mentioned is currently
available for Neutron.
There is perhaps a proposal from vArmour for a l3 plugin implementation,
but nothing merged so far.
For your question on effort, it is impossible to say whether it's a matter
of days or m
Hi Varun,
When Neutron is enabled, the last 3 octects of the MAC address are randomly
generated.
This is for avoiding clashes when instances are created concurrently and
for preventing potentially malicious users from guessing other users' MAC
addresses.
Any change to this logic will need code ch
Hi Nishant,
unfortunately Neutron at the moment supports only a single plugin for each
service. This means you can only specify a single core_plugin.
If your goal is to support multiple backend technologies in your
deployment, you should perhaps have a look at the ML2 where deployment of
multiple
It seems to me that those extensions (the one you list in the first post on
this thread) are not supported by the ML2 plugin.
Some of them like port-security are supported only by some core plugins (in
that case Nicira).
Other extensions, such as metering, are enabled through service plugins,
which
Comments inline.
Salvatore
On 25 March 2014 07:03, Ageeleshwar Kandavelu <
ageeleshwar.kandav...@csscorp.com> wrote:
> Hi,
>
> I have two queries regarding neutron ovs agent.
>
> 1. Correct me if I am wrong the ovs agent polls the neutron database for
> changes before creating resources. Why do
Hi Jeff,
in a nutshell, Neutron has its IPAM logic baked into the main 'db class'.
However, Neutron's IPAM does not manage at all the underlay - it manages
exclusively devices in the 'logical' realm.
There are been discussions in the past concerning Physical appliance
management in Neutron, not j
Hi,
it would be good if you can confirm whether this behaviour affects icehouse
or trunk as well.
Several bugs concerning nova/neutron communication as well as ovs agent
handling of ports have been fixed during the last two release cycle.
While the stable team did a great job in back-porting those
Some (hopefully) helpful answer inline.
Salvatore
On 6 October 2014 22:45, Mike Spreitzer wrote:
> Is it possible to use DevStack to install OpenStack, including Neutron, so
> that OpenStack can make a VM that can communicate with the world beyond
> OpenStack? I am looking for a simple localr
I think you do not have a l3 plugin configured in your neutron.conf -
therefore the l3 extension is not being loaded and the router resource does
not exist.
If the l3 plugin is not there just add it to service_plugins.
If the diagnosis is correct, can you post this question to ask.openstack.org
(i
On 21 November 2014 10:35, Antonio Messina
wrote:
> Hi all,
>
> I'm running a Juno testbed with Neutron, ml2 and ovs. We have use
> cases where we would like to create a shared vlan network and directly
> attach a VM on this network. This is not hard to do, and I've
> described how I did at this
Afaict infoblox integration cannot work with "stock" openstack components.
I think you'll need a service plugin and additional logic to bypass
Neutron's "baked" IPAM logic, and a modified DHCP agent to support relay.
The community is working on solution for integrating neutron with 3rd party
IPAM
6 minutes is surely the symptom of something wrong. The RPC is
asynchronous. A router_updated notification is sent from the server side as
soon as the floating IP is associated.
The l3 agent apparently is either missing or processing this notification
with a huge delay. Indeed the floating IP might
Silvia,
Unfortunately this log snippet just tells us that Neutron failed at startup.
There might be more information in the Neutron log. As the service failed
to start you should see a traceback in q-svc.log (or whatever name you have
for neutron's screen log).
Regards,
Salvatore
On 6 May 2015 a
Perhaps you can achieve this by editing policy.json (located by default in
/etc/neutron).
For instance you can allow only admin users to add security group rules to
any security group by specifying the following:
"create_security_group_rule": "admin_only"
Similar rules for update and deletion of
I would check for errors in the nova compute logs.
In some cases I had the same error, but the actual root cause was that the
nova compute log was failing to setup networking for an instance. The
request went back to the scheduler, which selected another compute node,
but failed in the same way wh
y sounded quite dumb and irritating.
Salvatore
On 22 June 2015 at 09:14, Silvia Fichera wrote:
> Good morning.
> As I told I can't find the folder /var/log/nova.
> So which log should I check?
> Thanks
>
> 2015-06-19 16:23 GMT+02:00 Salvatore Orlando :
>
>&g
If I understand correctly your use case security groups can be probably
used to satisfy your goal with Neutron.
Groups of isolated VMs in the same network can be assigned to different
security groups. Traffic among different groups will be dropped unless
unable by a specific security group rule.
Hello Marco,
more comments inline.
Salvatore
On 7 July 2015 at 22:09, Marco Mariani wrote:
> 2015-07-07 20:52 GMT+02:00 Salvatore Orlando :
>
> If I understand correctly your use case security groups can be probably
>> used to satisfy your goal with Neutron.
>>
>>
35 matches
Mail list logo
