+1
__
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
+1
__
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
+1
/sv
__
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
>
> eth0 : Admin ( PXE), Management (101), Storage (102), Internal (1000-1030)
> eth1 : External ( Public )
> eth2 : None
>
> I am using *fuel 9.0* and i want to use provider network / Multiple
> external networks with fuel. i had vlan networks on *eth1* as below
>
> *eth1 : 192.168.200.0/24
+1
/sv
__
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
+1
/sv
On Jun 9, 2016 09:24, "Julia Aranovich" wrote:
> +1
>
> On Wed, Jun 8, 2016 at 8:52 PM Bulat Gaifullin
> wrote:
>
>> Hey Fuelers,
>>
>> I'd like to nominate Ilya Kutukov for the fuel-web-core team.
>> Ilya`s doing good reviews with
Keys should be immutable.
If keys are not immutable -- it can lead to the situation, when
network_metadata/nodes contains two records for same nodes (with same UID),
but with different information.
/sv
__
OpenStack
+1
/sv
__
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
On Fri, Nov 20, 2015 at 4:00 PM, Alexey Shtokolov
wrote:
> Probably we should use another keyword for Fuel CI to prevent an extra
> load on the infrastructure? For example "refuel" or smth like this?
IMHO we should have ability to restart each one of two deployment
On Wed, Nov 11, 2015 at 1:41 PM, Daniel Depaoli <
daniel.depa...@create-net.org> wrote:
> Hi all.
> I'm starting to resolve the todo at these line[1]. To solve this I think
> to hardcoded the role in the file, for example:
>
> *$swift_proxies = get_nodes_hash_by_roles($network_metadata,
>
On Thu, Oct 22, 2015 at 6:16 AM, Matt Fischer wrote:
> I thought we had code in other places that split out stderr and only
> logged it if there was an actual error but I cannot find the reference now.
> I think that matches the original proposal. Not sure I like idea #3.
Hi, guys!
Now I observe potential-dangerous situation in the providers of
puppet-neutron module. I want share details, because not only
puppet-neutron module may be broken by warnings from Openstack CLI
utilities.
After updating urllib3 library on my lab, commands like 'neutron net list'
began
>
> >I would like to pay your attention to the changing interface naming
> >schema, which is proposed to be implemented in FuelA [1].A In brief,
> >Ethernet network interfaces may not be named as ethX, and there is a
> >reported bug about itA [2]
> >There are a lot of reasons
On Mon, Oct 5, 2015 at 12:22 PM, Eugene Nikanorov
wrote:
> No pacemaker for os services, please.
> We'll be moving out neutron agents from pacemaker control in 8.0, other os
> services don't need it too.
>
could you please provide your arguments.
/sv
On Fri, Oct 2, 2015 at 10:50 PM, Alex Schultz wrote:
> So I was working on Bug 1493520 which is about what happens when a
> controller runs out of space. For this I came up with a solution[1] to
> leverage pacemaker to migrate services away from the controller when
> it
+1
/sv
__
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
+1
/sv
__
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
+1
/sv
__
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
On Wed, Jul 29, 2015 at 7:08 AM, Mike Scherbakov mscherba...@mirantis.com
wrote:
Looks like Fuel Menu can't solve this one. Is there workaround possible
(even with worse UX)?
add to fuel-menu ability to load yaml file with network scheme.
However, I can't predict how serial console can live
-1 to Maciej
+1 to Sergii
/sv
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
On Wed, Jul 29, 2015 at 12:01 PM, Sergii Golovatiuk
sgolovat...@mirantis.com wrote:
add to fuel-menu ability to load yaml file with network scheme.
However, I can't predict how serial console can live with zmodem (or
something else serial communication protocol) on the same serial port.
On Mon, Jul 27, 2015 at 1:10 PM, Evgeniy L e...@mirantis.com wrote:
Currently network template uses ERB [1] style template language,
but in fact it's Jinja [2], it was agreed to change it [3], no to confuse
the user, with ERB which is in fact jinja and doesn't have any ERB
features.
we have
On Tue, Jul 28, 2015 at 11:52 AM, Evgeniy L e...@mirantis.com wrote:
Hi Alexander, I don't agree with your statements
[1] - I just uses % and % to substitute values.
It's what templating is about, you have some text preprocessor to
substitute values.
Network templates feature don't mean
If we need only substitution, probably it's better to use standard
templating
in python [1], there is a way to redefine tokens, so you will be able to
use
% % syntax if you want to.
[1] https://docs.python.org/2.6/library/string.html#template-strings
On Tue, Jul 28, 2015 at 7:13 PM, Aleksey Kasatkin akasat...@mirantis.com
wrote:
Evgeniy, do we need to remove jinja before July 30th ?
I think -- not.
It just a bug, not a key-point of feature.
/sv
__
OpenStack
+1
__
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
On Thu, Jul 16, 2015 at 10:53 PM, Andrew Woodward xar...@gmail.com wrote:
Regardless of computing all the routes, we need to compute same role, but
multi-segement routes. In this case I see that nodegroups becomes
redundant. It's only value is that it may be a simpler interface then
templates
+1
__
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
I notice that in OpenStack deployed by Fuel, Ceph public network is on
management network.
As I know separating cuph/public and management networks in a scope of 7.0
release.
/sv
__
OpenStack Development Mailing List
+1
__
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
+1
/sv
On Fri, Mar 27, 2015 at 5:31 PM, Anastasia Urlapova aurlap...@mirantis.com
wrote:
+ 10
On Fri, Mar 27, 2015 at 4:28 AM, Igor Zinovik izino...@mirantis.com
wrote:
+1
On 26 March 2015 at 19:26, Fabrizio Soppelsa fsoppe...@mirantis.com
wrote:
+1 definitely
On 03/25/2015
+1, sorting is should be...
Paginating may be too, but not activated by default.
/sv
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
+1 to replace simple to HA with one controller
/sv
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
Guys, it's a big and complicated architecture issue.
Issue, like this was carefully researched about month ago (while P***)
root case of issue:
- Now we use OVS for build virtual network topology on each node.
- OVS has performance degradation while pass huge of small network
packets.
Nor should it, IMO. Other than the Neutron dhcp-agent, all OpenStack
services that run on a controller node are completely stateless.
Therefore, I don't see any reason to use corosync/pacemaker for management
of these resources.
I see following reasons for managing neutron agents by
On Wed, Aug 27, 2014 at 2:11 AM, David Easter deas...@mirantis.com wrote:
What’s New in Fuel 5.1?
The primary new features of Fuel 5.1 are:
* Compute, cinder, ceph nodes has no external (public) network interface
and don't get public IP addresses if it's not necessary.
/sv
[1] fixed in https://review.openstack.org/#/c/107046/
Thanks for report a bug.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
After review https://review.openstack.org/#/c/103280/ I have following
thoughts. This patch looks fine, but huge and has lot of changes in
deployment logic. Parallel teams work (vmware, melanox) depends on current
implementation of Neutron in FUEL. I have a some dreads, that they can’t
refactor
38 matches
Mail list logo