[Openstack-operators] OpenStack Liberty RC1 for Ubuntu 14.04 LTS and Ubuntu 15.10

2015-10-02 Thread James Page 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi All

The Ubuntu OpenStack Engineering team is pleased to announce the
general availability of the first release candidates for the OpenStack
Liberty release in Ubuntu 15.10 development and for Ubuntu 14.04 LTS
via the Ubuntu Cloud Archive.

Further release candidates will be pushed to the archives as and when
they appear.

Ubuntu 14.04 LTS
- 

You can enable the Ubuntu Cloud Archive for OpenStack Liberty on
Ubuntu 14.04 installations by running the following commands (make
sure you have an up-to-date software-properties-common package first):

  sudo add-apt-repository cloud-archive:liberty
  sudo apt-get update

The Ubuntu Cloud Archive for Liberty includes updates for Nova,
Glance, Keystone, Neutron, Cinder, Swift, Horizon, Ceilometer, Heat,
Designate, Barbican, Manila, Ironic, Trove and Sahara; Ceph (0.94.3),
RabbitMQ (3.5.4), QEMU (2.3), libvirt (1.2.16) and OpenvSwitch (2.4.0)
backports from Ubuntu 15.10 development have also been provided.

You can checkout the full list of packages and versions at [0].

Ubuntu 15.10 (Wily) development
- ---

No extra steps required; just start installing OpenStack!

Reporting bugs
- --

Any issues please report bugs using the 'ubuntu-bug' tool:

  sudo ubuntu-bug nova-conductor

this will ensure that bugs get logged in the right place in Launchpad
- - and come poke any of my team (zul, coreycb, gnuoy, thedac, ddellav
or beisner) in #ubuntu-server if something is particularly annoying or
broken…

Finally - thank you to everyone who’s made OpenStack Liberty RC1 a
reality - and have fun!

Cheers

James

[0]
http://reqorts.qa.ubuntu.com/reports/ubuntu-server/cloud-archive/liberty
_versions.html

- -- 
James Page
Ubuntu and Debian Developer
james.p...@ubuntu.com
jamesp...@debian.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWDm1kAAoJEL/srsug59jDDO8QAIiv82Z7MiOdssAiN1jktbCE
6etKZE4mM2CqF91t1NYDNkjGbQvEYfFI1PpNrSd0HmLuybkMR0XEQj07oPhTgdJd
HUFvXwJBPzsPa2mBer5WylQz4RAuVBfdIanjvgAa4My/SvoLFDFjeSqXj0sYSBgC
VyGPdpk6c5NwkzaxsAYL7TB/BWGFzDWeht9YF4wNyvxzGQOhyMkxRvQ2VMRUMxHt
6z8iR+vSENoHzrV0UPt4wTG8L51ZkXv+TaC8pXZTEtSWTGjaOxEa0YMjX5I/bNwX
y3VkuOmoXn+6lshBNJrri8Mr/KtwrWAZ/+UnwT8GmwbPVQ49tdCd0hFC5LRBC7cR
fneEcGBcOxJ4ftzJP5HOz3ZnFH7szvSAfmPrdDCDvuN0bpCHuCbi6dPAjse3MqVp
LIKNWPSD1BEzPUONF4y+/9iIpEEPHt6ehxBu/i9i0fLt4/KYd51GuR+rl/ZvQjn4
G2tnTEuKn+2znT2D+Y2LyQgEZlIThewZJFUuTq5s+B3KhZ0orCuvRvY0qJMyHS0A
TA1XGxTEOp5DZVzVy0/rCyp5V316u//a4lSPHuP+1aneV2q7T3CkafjgNScG/P8h
wAg0clhe5vWeMMDlgooBEsOYak+AFObdtojpDTaVmtfEbUbwpRZ77/SnhWm7pBlA
M8C8gWQojDXLHD7Cox1s
=CPST
-END PGP SIGNATURE-

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

[Openstack-operators] heat stack update

2015-10-02 Thread Ignazio Cassano 
I everybody,
I really did not undarstand what can I do updataing a heat stack.
If I create a simple stack with a virtual machine and a cinder volume
attacched , can
I add a new volume updating the stack ?
Or can I resize the existing volume updating the stack ?
Or updating the stack the virtual machine is rebuilded ?
Regards
Ignazio
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [Neutron][Linuxbridge] Problem with configuring linux bridge agent with vxlan networks

2015-10-02 Thread Sławek Kapłoński 
Hello,

I'm trying to configure small openstack infra (one network node, 2
compute nodes) with linux bridge and vxlan tenant networks. I don't know
what I'm doing wrong but my instances have no connection between
each other. On compute hosts I run neutron-plugin-linuxbrigde-agent
with config like:

--
[ml2_type_vxlan]
# (ListOpt) Comma-separated list of : tuples
# enumerating
# ranges of VXLAN VNI IDs that are available for tenant network
# allocation.
#
vni_ranges = 1:2

# (StrOpt) Multicast group for the VXLAN interface. When configured,
# will
# enable sending all broadcast traffic to this multicast group. When
# left
# unconfigured, will disable multicast VXLAN mode.
#
# vxlan_group =
# Example: vxlan_group = 239.1.1.1

[securitygroup]
# Controls if neutron security group is enabled or not.
# It should be false when you use nova security group.
enable_security_group = True

# Use ipset to speed-up the iptables security groups. Enabling ipset
# support
# requires that ipset is installed on L2 agent node.
enable_ipset = True

firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver

[ovs]
local_ip = 10.1.0.4

[agent]
tunnel_types = vxlan

[linuxbridge]
physical_interface_mappings = physnet1:eth1

[vxlan]
local_ip = 10.1.0.4
l2_population = True
enable_vxlan = True
---

Eth1 is my "tunnel network" which should be used for tunnels. When I
spawn vms on compute 1 and 2 and after configuring network manually on
both vms (dhcp is not working also because of broken tunnels probably)
it not pings.
Even when I started two instances on same host and they are both
connected to one bridge:

---
root@compute-2:/usr/lib/python2.7/dist-packages/neutron# brctl show
bridge name bridge id   STP enabled interfaces
brq8fe8a32f-e6  8000.ce544d0c0e5d   no  tap691a138a-6c
tapbc1e5179-53
vxlan-10052
virbr0  8000.5254007611ab   yes virbr0-nic
---

those 2 vms are not pinging each other :/
I don't have any expeirence with linux bridge in fact (For now I was always
using ovs). Maybe someone of You will know what I should check or what I should
configure wrong :/ Generally I was installing this openstack according to
official openstack documentation but in this docs there is info about ovs+gre
tunnels and that is what I changed. I'm using Ubuntu 14.04 and Openstack Kilo
installed from cloud archive repo.

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl



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

Re: [Openstack-operators] [Neutron][Linuxbridge] Problem with configuring linux bridge agent with vxlan networks

2015-10-02 Thread Matt Kassawara 
Did you review the scenarios in the networking guide [1]?

[1] http://docs.openstack.org/networking-guide/deploy.html

On Fri, Oct 2, 2015 at 2:41 PM, Sławek Kapłoński 
wrote:

> Hello,
>
> I'm trying to configure small openstack infra (one network node, 2
> compute nodes) with linux bridge and vxlan tenant networks. I don't know
> what I'm doing wrong but my instances have no connection between
> each other. On compute hosts I run neutron-plugin-linuxbrigde-agent
> with config like:
>
> --
> [ml2_type_vxlan]
> # (ListOpt) Comma-separated list of : tuples
> # enumerating
> # ranges of VXLAN VNI IDs that are available for tenant network
> # allocation.
> #
> vni_ranges = 1:2
>
> # (StrOpt) Multicast group for the VXLAN interface. When configured,
> # will
> # enable sending all broadcast traffic to this multicast group. When
> # left
> # unconfigured, will disable multicast VXLAN mode.
> #
> # vxlan_group =
> # Example: vxlan_group = 239.1.1.1
>
> [securitygroup]
> # Controls if neutron security group is enabled or not.
> # It should be false when you use nova security group.
> enable_security_group = True
>
> # Use ipset to speed-up the iptables security groups. Enabling ipset
> # support
> # requires that ipset is installed on L2 agent node.
> enable_ipset = True
>
> firewall_driver =
> neutron.agent.linux.iptables_firewall.IptablesFirewallDriver
>
> [ovs]
> local_ip = 10.1.0.4
>
> [agent]
> tunnel_types = vxlan
>
> [linuxbridge]
> physical_interface_mappings = physnet1:eth1
>
> [vxlan]
> local_ip = 10.1.0.4
> l2_population = True
> enable_vxlan = True
> ---
>
> Eth1 is my "tunnel network" which should be used for tunnels. When I
> spawn vms on compute 1 and 2 and after configuring network manually on
> both vms (dhcp is not working also because of broken tunnels probably)
> it not pings.
> Even when I started two instances on same host and they are both
> connected to one bridge:
>
> ---
> root@compute-2:/usr/lib/python2.7/dist-packages/neutron# brctl show
> bridge name bridge id   STP enabled interfaces
> brq8fe8a32f-e6  8000.ce544d0c0e5d   no
> tap691a138a-6c
> tapbc1e5179-53
> vxlan-10052
> virbr0  8000.5254007611ab   yes virbr0-nic
> ---
>
> those 2 vms are not pinging each other :/
> I don't have any expeirence with linux bridge in fact (For now I was always
> using ovs). Maybe someone of You will know what I should check or what I
> should
> configure wrong :/ Generally I was installing this openstack according to
> official openstack documentation but in this docs there is info about
> ovs+gre
> tunnels and that is what I changed. I'm using Ubuntu 14.04 and Openstack
> Kilo
> installed from cloud archive repo.
>
> --
> Best regards / Pozdrawiam
> Sławek Kapłoński
> sla...@kaplonski.pl
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [Neutron][Linuxbridge] Problem with configuring linux bridge agent with vxlan networks

2015-10-02 Thread Sławek Kapłoński 
Hello,

Yes. I was reading mostly
http://docs.openstack.org/networking-guide/scenario_legacy_lb.html
because imho this is what I want now :). I don't want DVR and L3 HA (at
least for now) but only traffic via vxlan between two vms which are
connected to tenant network (it is probably called east-west traffic,
yes?)

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Fri, 02 Oct 2015, Matt Kassawara wrote:

> Did you review the scenarios in the networking guide [1]?
> 
> [1] http://docs.openstack.org/networking-guide/deploy.html
> 
> On Fri, Oct 2, 2015 at 2:41 PM, Sławek Kapłoński 
> wrote:
> 
> > Hello,
> >
> > I'm trying to configure small openstack infra (one network node, 2
> > compute nodes) with linux bridge and vxlan tenant networks. I don't know
> > what I'm doing wrong but my instances have no connection between
> > each other. On compute hosts I run neutron-plugin-linuxbrigde-agent
> > with config like:
> >
> > --
> > [ml2_type_vxlan]
> > # (ListOpt) Comma-separated list of : tuples
> > # enumerating
> > # ranges of VXLAN VNI IDs that are available for tenant network
> > # allocation.
> > #
> > vni_ranges = 1:2
> >
> > # (StrOpt) Multicast group for the VXLAN interface. When configured,
> > # will
> > # enable sending all broadcast traffic to this multicast group. When
> > # left
> > # unconfigured, will disable multicast VXLAN mode.
> > #
> > # vxlan_group =
> > # Example: vxlan_group = 239.1.1.1
> >
> > [securitygroup]
> > # Controls if neutron security group is enabled or not.
> > # It should be false when you use nova security group.
> > enable_security_group = True
> >
> > # Use ipset to speed-up the iptables security groups. Enabling ipset
> > # support
> > # requires that ipset is installed on L2 agent node.
> > enable_ipset = True
> >
> > firewall_driver =
> > neutron.agent.linux.iptables_firewall.IptablesFirewallDriver
> >
> > [ovs]
> > local_ip = 10.1.0.4
> >
> > [agent]
> > tunnel_types = vxlan
> >
> > [linuxbridge]
> > physical_interface_mappings = physnet1:eth1
> >
> > [vxlan]
> > local_ip = 10.1.0.4
> > l2_population = True
> > enable_vxlan = True
> > ---
> >
> > Eth1 is my "tunnel network" which should be used for tunnels. When I
> > spawn vms on compute 1 and 2 and after configuring network manually on
> > both vms (dhcp is not working also because of broken tunnels probably)
> > it not pings.
> > Even when I started two instances on same host and they are both
> > connected to one bridge:
> >
> > ---
> > root@compute-2:/usr/lib/python2.7/dist-packages/neutron# brctl show
> > bridge name bridge id   STP enabled interfaces
> > brq8fe8a32f-e6  8000.ce544d0c0e5d   no
> > tap691a138a-6c
> > tapbc1e5179-53
> > vxlan-10052
> > virbr0  8000.5254007611ab   yes virbr0-nic
> > ---
> >
> > those 2 vms are not pinging each other :/
> > I don't have any expeirence with linux bridge in fact (For now I was always
> > using ovs). Maybe someone of You will know what I should check or what I
> > should
> > configure wrong :/ Generally I was installing this openstack according to
> > official openstack documentation but in this docs there is info about
> > ovs+gre
> > tunnels and that is what I changed. I'm using Ubuntu 14.04 and Openstack
> > Kilo
> > installed from cloud archive repo.
> >
> > --
> > Best regards / Pozdrawiam
> > Sławek Kapłoński
> > sla...@kaplonski.pl
> >
> >
> > ___
> > OpenStack-operators mailing list
> > OpenStack-operators@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> >
> >


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

[Openstack-operators] OpenStack Community Weekly Newsletter (September 28 - October 2)

2015-10-02 Thread Allison Price 
53 things that are new in OpenStack Liberty 

Another autumn, another OpenStack release. OpenStack’s 12th release, Liberty, 
is due on October 15, and release candidates are already being made available. 
But what can we expect from the last six months of development?

App Developers: First App on OpenStack Tutorial Needs You 

The tutorial that guides new developers to deploy their first application on 
OpenStack is complete for Apache Libcloud and needs help for new languages and 
SDKs.

The Road to Tokyo 

The OpenStack Summit Tokyo will sell out! Register NOW! 
 
The deadline to request transfers and refunds is October 12. Please email 
summit...@openstack.org  with any requests or 
questions.
The schedule and mobile app for the OpenStack Summit in Tokyo are now available 
 
Speakers, sponsors, and ATC registration codes must be redeemed by October 19 
at 11:59 p.m. PT, so register now!
Community Feedback

OpenStack is always interested in feedback and community contributions, if you 
would like to see a new section in the OpenStack Weekly Community Newsletter or 
have ideas on how to present content please get in touch: 
commun...@openstack.org .
Reports from Previous Events 

None this week
Deadlines and Contributors Notifications 

Liberty Release Oct., 15, 2015 

Security Advisories and Notices 

[openstack-announce] [OSSA 2015-020] Glance storage overrun (CVE-2015-5286) 

Tips ‘n Tricks 

By Augustina Ragwitz 
: 
Hack hack hack the way to your first OpenStack patch 

By Scott Lowe: Using Docker Machine with OpenStack 

Upcoming Events  

Oct 04 – 08, 2015 Gartner SymposiumITxpo Orlando, FL, US 

Oct 06, 2015 October Sydney Meetup 

Oct 07, 2015 Houston OpenStack Meetup Houston, TX, US 

Oct 07 – 08, 2015 OpenStack Liberty Release Richardson, TX, US 

Oct 07 – 08, 2015 OpenStack 101 Houston, TX, US 

Oct 08, 2015 7. Meetup, Konu : Murano - OpenStack App Catalog Ankara, TR 

Oct 08 - 09, 2015 Neutron apollozza! New date! New Location! Austin, TX, US 

Oct 10, 2015 OpenStack India Meetup, Pune, IN 

Oct 12, 2015 OpenStack Cinder deep dive Stockholm, SE 


What you need to know from the developer’s list

PTL election results are in!
https://wiki.openstack.org/wiki/PTL_Elections_September_2015#Results 


Proposed Design Summit track/room/time allocation 

http://tinyurl.com/mitaka-design-summit 
 
If anyone sees any glaring issues, they should reach out to Thierry Carrez.

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

Re: [Openstack-operators] [Neutron][Linuxbridge] Problem with configuring linux bridge agent with vxlan networks

2015-10-02 Thread James Denton 
If eth1 is used for the vxlan tunnel end points, it can't also be used in a 
bridge ala provider_bridge_mappings. You should have a dedicated interface or a 
vlan interface off eth1 (i.e. Eth1.20) that is dedicated to the overlay 
traffic. Move the local_ip address to that interface on respective nodes. 
Verify that you can ping between nodes at each address. If this doesn't work, 
the Neutron pieces won't work. You shouldn't have to restart any neutron 
services, since the IP isn't changing.

Once you create a vxlan tenant network and boot some instances, verify that the 
vxlan interface is being setup and placed in the respective bridge. You can use 
'brctl show' to look at the brq bridge that corresponds to the network. You 
should see a vxlan interface and the tap interfaces of your instances. 

As always, verify your security groups first when troubleshooting instance to 
instance communication.

James

Sent from my iPhone

> On Oct 2, 2015, at 3:48 PM, Sławek Kapłoński  wrote:
> 
> Hello,
> 
> I'm trying to configure small openstack infra (one network node, 2
> compute nodes) with linux bridge and vxlan tenant networks. I don't know
> what I'm doing wrong but my instances have no connection between
> each other. On compute hosts I run neutron-plugin-linuxbrigde-agent
> with config like:
> 
> --
> [ml2_type_vxlan]
> # (ListOpt) Comma-separated list of : tuples
> # enumerating
> # ranges of VXLAN VNI IDs that are available for tenant network
> # allocation.
> #
> vni_ranges = 1:2
> 
> # (StrOpt) Multicast group for the VXLAN interface. When configured,
> # will
> # enable sending all broadcast traffic to this multicast group. When
> # left
> # unconfigured, will disable multicast VXLAN mode.
> #
> # vxlan_group =
> # Example: vxlan_group = 239.1.1.1
> 
> [securitygroup]
> # Controls if neutron security group is enabled or not.
> # It should be false when you use nova security group.
> enable_security_group = True
> 
> # Use ipset to speed-up the iptables security groups. Enabling ipset
> # support
> # requires that ipset is installed on L2 agent node.
> enable_ipset = True
> 
> firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver
> 
> [ovs]
> local_ip = 10.1.0.4
> 
> [agent]
> tunnel_types = vxlan
> 
> [linuxbridge]
> physical_interface_mappings = physnet1:eth1
> 
> [vxlan]
> local_ip = 10.1.0.4
> l2_population = True
> enable_vxlan = True
> ---
> 
> Eth1 is my "tunnel network" which should be used for tunnels. When I
> spawn vms on compute 1 and 2 and after configuring network manually on
> both vms (dhcp is not working also because of broken tunnels probably)
> it not pings.
> Even when I started two instances on same host and they are both
> connected to one bridge:
> 
> ---
> root@compute-2:/usr/lib/python2.7/dist-packages/neutron# brctl show
> bridge namebridge idSTP enabledinterfaces
> brq8fe8a32f-e68000.ce544d0c0e5dnotap691a138a-6c
>tapbc1e5179-53
>vxlan-10052
> virbr08000.5254007611abyesvirbr0-nic
> ---
> 
> those 2 vms are not pinging each other :/
> I don't have any expeirence with linux bridge in fact (For now I was always
> using ovs). Maybe someone of You will know what I should check or what I 
> should
> configure wrong :/ Generally I was installing this openstack according to
> official openstack documentation but in this docs there is info about ovs+gre
> tunnels and that is what I changed. I'm using Ubuntu 14.04 and Openstack Kilo
> installed from cloud archive repo.
> 
> -- 
> Best regards / Pozdrawiam
> Sławek Kapłoński
> sla...@kaplonski.pl
> 
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

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

Re: [Openstack-operators] [Neutron][Linuxbridge] Problem with configuring linux bridge agent with vxlan networks

2015-10-02 Thread Mike Lowe 
One thing that I always forget is iptables rules to allow the udp port 8472 
vxlan packets in.

> On Oct 2, 2015, at 4:41 PM, Sławek Kapłoński  wrote:
> 
> Hello,
> 
> I'm trying to configure small openstack infra (one network node, 2
> compute nodes) with linux bridge and vxlan tenant networks. I don't know
> what I'm doing wrong but my instances have no connection between
> each other. On compute hosts I run neutron-plugin-linuxbrigde-agent
> with config like:
> 
> --
> [ml2_type_vxlan]
> # (ListOpt) Comma-separated list of : tuples
> # enumerating
> # ranges of VXLAN VNI IDs that are available for tenant network
> # allocation.
> #
> vni_ranges = 1:2
> 
> # (StrOpt) Multicast group for the VXLAN interface. When configured,
> # will
> # enable sending all broadcast traffic to this multicast group. When
> # left
> # unconfigured, will disable multicast VXLAN mode.
> #
> # vxlan_group =
> # Example: vxlan_group = 239.1.1.1
> 
> [securitygroup]
> # Controls if neutron security group is enabled or not.
> # It should be false when you use nova security group.
> enable_security_group = True
> 
> # Use ipset to speed-up the iptables security groups. Enabling ipset
> # support
> # requires that ipset is installed on L2 agent node.
> enable_ipset = True
> 
> firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver
> 
> [ovs]
> local_ip = 10.1.0.4
> 
> [agent]
> tunnel_types = vxlan
> 
> [linuxbridge]
> physical_interface_mappings = physnet1:eth1
> 
> [vxlan]
> local_ip = 10.1.0.4
> l2_population = True
> enable_vxlan = True
> ---
> 
> Eth1 is my "tunnel network" which should be used for tunnels. When I
> spawn vms on compute 1 and 2 and after configuring network manually on
> both vms (dhcp is not working also because of broken tunnels probably)
> it not pings.
> Even when I started two instances on same host and they are both
> connected to one bridge:
> 
> ---
> root@compute-2:/usr/lib/python2.7/dist-packages/neutron# brctl show
> bridge name   bridge id   STP enabled interfaces
> brq8fe8a32f-e68000.ce544d0c0e5d   no  
> tap691a138a-6c
>   tapbc1e5179-53
>   vxlan-10052
> virbr08000.5254007611ab   yes virbr0-nic
> ---
> 
> those 2 vms are not pinging each other :/
> I don't have any expeirence with linux bridge in fact (For now I was always
> using ovs). Maybe someone of You will know what I should check or what I 
> should
> configure wrong :/ Generally I was installing this openstack according to
> official openstack documentation but in this docs there is info about ovs+gre
> tunnels and that is what I changed. I'm using Ubuntu 14.04 and Openstack Kilo
> installed from cloud archive repo.
> 
> -- 
> Best regards / Pozdrawiam
> Sławek Kapłoński
> sla...@kaplonski.pl
> 
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators



smime.p7s
Description: S/MIME cryptographic signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [neutron] - deprecation of max_fixed_ips_per_port

2015-10-02 Thread Kevin Benton 
Hi,

There is an option in Neutron called max_fixed_ips_per_port that limits the
number of IP addresses that can be assigned to each port. It doesn't appear
to have a clear use case since we prevent users from setting IPs on ports
attached to networks they don't own (shared networks). I have filed a
bug[1] to deprecate it for removal in N.

If you have a use case for max_fixed_ips_per_port that I am missing, please
provide feedback on the bug report.


1. https://bugs.launchpad.net/neutron/+bug/1502356

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

Re: [Openstack-operators] heat stack update

2015-10-02 Thread Chris Buccella 
Hi Ignazio,

IIRC, the affect on stack resources will depend on what is being updated.
For example, adding or removing a floating IP to a nova instance can happen
without interrupting the running instance, but updating the instance image
would affect the running instance.

When in doubt, try it (-:


-Chris

On Fri, Oct 2, 2015 at 3:30 PM, Ignazio Cassano 
wrote:

> I everybody,
> I really did not undarstand what can I do updataing a heat stack.
> If I create a simple stack with a virtual machine and a cinder volume
> attacched , can
> I add a new volume updating the stack ?
> Or can I resize the existing volume updating the stack ?
> Or updating the stack the virtual machine is rebuilded ?
> Regards
> Ignazio
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators