Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Bogdan Dobrelya]

+1

On 25.08.2016 21:08, Stanislaw Bogatkin wrote:
> +1
> 
> On Thu, Aug 25, 2016 at 12:08 PM, Aleksandr Didenko
> > wrote:
> 
> +1
> 
> On Thu, Aug 25, 2016 at 9:35 AM, Sergey Vasilenko
> > wrote:
> 
> +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 
> 
> 
> 
> 
> __
> 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
> 
> 
> 
> 
> 
> -- 
> with best regards,
> Stan.
> 
> 
> __
> 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
> 


-- 
Best regards,
Bogdan Dobrelya,
Irc #bogdando

__
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] [fuel] Propose Denis Egorenko for fuel-library core

[Stanislaw Bogatkin]

+1

On Thu, Aug 25, 2016 at 12:08 PM, Aleksandr Didenko 
wrote:

> +1
>
> On Thu, Aug 25, 2016 at 9:35 AM, Sergey Vasilenko  > wrote:
>
>> +1
>>
>>
>> /sv
>>
>>
>> 
>> __
>> 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
>
>


-- 
with best regards,
Stan.
__
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] [fuel] Propose Denis Egorenko for fuel-library core

[Aleksandr Didenko]

+1

On Thu, Aug 25, 2016 at 9:35 AM, Sergey Vasilenko 
wrote:

> +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
>
>
__
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] [fuel] Propose Denis Egorenko for fuel-library core

[Sergey Vasilenko]

+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

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Maksim Malchuk]

My big +1

On Thu, Aug 25, 2016 at 4:13 AM, Emilien Macchi  wrote:

> I'm surprised Denis was not core before.
> He has been a tremendous core reviewer for the Puppet OpenStack modules.
>
> My vote doesn't count but I'm still encouraging this effort. Congrats
> Denis, it's well deserved!
>
> On Wed, Aug 24, 2016 at 5:33 PM, Sergii Golovatiuk
>  wrote:
> > +1
> >
> > --
> > Best regards,
> > Sergii Golovatiuk,
> > Skype #golserge
> > IRC #holser
> >
> > On Wed, Aug 24, 2016 at 10:49 PM, Matthew Mosesohn <
> mmoses...@mirantis.com>
> > wrote:
> >>
> >> +1 Denis is excellent at reviews and spotting CI failure root causes.
> >> I definitely support him.
> >>
> >> On Wed, Aug 24, 2016 at 11:36 PM, Alex Schultz 
> >> wrote:
> >> > Ahoy Fuel Cores,
> >> >
> >> > I would like to propose Denis Egorenko for fuel-library core.  Denis
> is
> >> > always providing great reviews[0] and continues to help keep Fuel
> moving
> >> > forward.  He's the #3 reviewer and committer of the last 90 days[1]
> and
> >> > 180
> >> > days[2].
> >> >
> >> > Please vote with a +1/-1. Voting will close on August 31st.
> >> >
> >> > Thanks,
> >> > -Alex
> >> >
> >> > [0] http://stackalytics.com/?user_id=degorenko
> >> > [1] http://stackalytics.com/report/contribution/fuel-library/90
> >> > [2] http://stackalytics.com/report/contribution/fuel-library/180
> >> >
> >> >
> >> > 
> __
> >> > 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
> >
>
>
>
> --
> Emilien Macchi
>
> __
> 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
>



-- 
Best Regards,
Maksim Malchuk,
Senior DevOps Engineer,
MOS: Product Engineering,
Mirantis, Inc

__
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] [fuel] Propose Denis Egorenko for fuel-library core

[Emilien Macchi]

I'm surprised Denis was not core before.
He has been a tremendous core reviewer for the Puppet OpenStack modules.

My vote doesn't count but I'm still encouraging this effort. Congrats
Denis, it's well deserved!

On Wed, Aug 24, 2016 at 5:33 PM, Sergii Golovatiuk
 wrote:
> +1
>
> --
> Best regards,
> Sergii Golovatiuk,
> Skype #golserge
> IRC #holser
>
> On Wed, Aug 24, 2016 at 10:49 PM, Matthew Mosesohn 
> wrote:
>>
>> +1 Denis is excellent at reviews and spotting CI failure root causes.
>> I definitely support him.
>>
>> On Wed, Aug 24, 2016 at 11:36 PM, Alex Schultz 
>> wrote:
>> > Ahoy Fuel Cores,
>> >
>> > I would like to propose Denis Egorenko for fuel-library core.  Denis is
>> > always providing great reviews[0] and continues to help keep Fuel moving
>> > forward.  He's the #3 reviewer and committer of the last 90 days[1] and
>> > 180
>> > days[2].
>> >
>> > Please vote with a +1/-1. Voting will close on August 31st.
>> >
>> > Thanks,
>> > -Alex
>> >
>> > [0] http://stackalytics.com/?user_id=degorenko
>> > [1] http://stackalytics.com/report/contribution/fuel-library/90
>> > [2] http://stackalytics.com/report/contribution/fuel-library/180
>> >
>> >
>> > __
>> > 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
>



-- 
Emilien Macchi

__
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] [fuel] Propose Denis Egorenko for fuel-library core

[Sergii Golovatiuk]

+1

--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser

On Wed, Aug 24, 2016 at 10:49 PM, Matthew Mosesohn 
wrote:

> +1 Denis is excellent at reviews and spotting CI failure root causes.
> I definitely support him.
>
> On Wed, Aug 24, 2016 at 11:36 PM, Alex Schultz 
> wrote:
> > Ahoy Fuel Cores,
> >
> > I would like to propose Denis Egorenko for fuel-library core.  Denis is
> > always providing great reviews[0] and continues to help keep Fuel moving
> > forward.  He's the #3 reviewer and committer of the last 90 days[1] and
> 180
> > days[2].
> >
> > Please vote with a +1/-1. Voting will close on August 31st.
> >
> > Thanks,
> > -Alex
> >
> > [0] http://stackalytics.com/?user_id=degorenko
> > [1] http://stackalytics.com/report/contribution/fuel-library/90
> > [2] http://stackalytics.com/report/contribution/fuel-library/180
> >
> > 
> __
> > 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

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Matthew Mosesohn]

+1 Denis is excellent at reviews and spotting CI failure root causes.
I definitely support him.

On Wed, Aug 24, 2016 at 11:36 PM, Alex Schultz  wrote:
> Ahoy Fuel Cores,
>
> I would like to propose Denis Egorenko for fuel-library core.  Denis is
> always providing great reviews[0] and continues to help keep Fuel moving
> forward.  He's the #3 reviewer and committer of the last 90 days[1] and 180
> days[2].
>
> Please vote with a +1/-1. Voting will close on August 31st.
>
> Thanks,
> -Alex
>
> [0] http://stackalytics.com/?user_id=degorenko
> [1] http://stackalytics.com/report/contribution/fuel-library/90
> [2] http://stackalytics.com/report/contribution/fuel-library/180
>
> __
> 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-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Alex Schultz]

Ahoy Fuel Cores,

I would like to propose Denis Egorenko for fuel-library core.  Denis is
always providing great reviews[0] and continues to help keep Fuel moving
forward.  He's the #3 reviewer and committer of the last 90 days[1] and 180
days[2].

Please vote with a +1/-1. Voting will close on August 31st.

Thanks,
-Alex

[0] http://stackalytics.com/?user_id=degorenko
[1] http://stackalytics.com/report/contribution/fuel-library/90
[2] http://stackalytics.com/report/contribution/fuel-library/180
__
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] [Fuel] Need Help in adding multiple External networks in Fuel 9.0

[Sergey Vasilenko]

>
> 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  ( Native ),
> 192.168.201.0/24  ( Trunk, 201 tagged ).
> 192.168.202.0/24  ( Trunk, 202 tagged )*
>
>
> How i can add other two networks( 201, 202 ) to my cloud as external
> network. appreciate anyone help on this.
>

For creating tagged vlans over external network you should:
1. modify /etc/neutron/plugin.ini to add vlan-range for physnet1, (ex:
network_vlan_ranges
= physnet1:201:202) and restart neutron-server on all controller nodes
2. Create additional floating networks by  Neutron API, ex: neutron
net-create floating201 --tenant-id=8a1d1a6f96db4beeb964a285e2a95413
 --router:external=true --provider:physical_network=physnet1
--provider:network_type=vlan --provider:segmentation_id=201
3. Create subnet for network above (ex: neutron subnet-create xxx1
--name=floating201_subnet --cidr=192.168.201.0/24
--network-id=8859c63e-c8e1-422c-9cda-d3e9d5ab6a20 --enable_dhcp=False
--gateway_ip=192.168.201.1)
4. Create router for handle SNAT:
# neutron router-create router201
--tenant-id=8a1d1a6f96db4beeb964a285e2a95413
# neutron router-gateway-set router201 floating201
# neutron router-interface-add router201 your_internal_net
__
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] [Fuel] Need Help in adding multiple External networks in Fuel 9.0

[Chandrasekhar Reddy]

Hi All,

I think this is right platform to ask my question. i will be thankful if
someone can help me in below mentioned use-case.

Here is my cloud setup:

I have 4 Nodes:

Controller Node : 1 No
Compute + Ceph Node : 2 No
Fuel Node : 1 No

My Interfaces are as below :

All 4 Nodes has *3 NIC cards * each.

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  ( Native ),
192.168.201.0/24  ( Trunk, 201 tagged ).
192.168.202.0/24  ( Trunk, 202 tagged )*


How i can add other two networks( 201, 202 ) to my cloud as external
network. appreciate anyone help on this.

Thanks,
Chandra.
__
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] [Fuel] Ocata design summit planning

[Vladimir Kozhukalov]

Dear colleagues,

We are two months from Ocata summit. Let's start planning topics we would
like to discuss during design sessions. Here is etherpad [1]. Please put
your topics under backlog section and we will disscuss later which of them
will be brought out to design sessions.

[1] https://etherpad.openstack.org/p/fuel-ocata-summit-planning


Vladimir Kozhukalov
__
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] [fuel] Meeting for Aug - 18 is canceled

[Andrew Woodward]

The agenda [1] for today's meeting has no items, so I'm calling it for the
meeting this week.

Please review your action items from last meeting and update the ML if you
haven't done so already

romcheg to annouunce fuel2 promotion and old fuel CLI removal on ML
akscram to send ML about moving cluster_upgrade extension
gkibardin to follow up on ML about mcollective config issues
xarses will update spec regarding release naming and summarize on ML

[1] https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
-- 

--

Andrew Woodward

Mirantis

Fuel Community Ambassador

Ceph Community
__
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] [Fuel] Getting rid of ISO

[Jay Pipes]

On 08/16/2016 04:58 AM, Vladimir Kozhukalov wrote:

Dear colleagues,

We finally have working custom deployment job that deploys Fuel admin
node using online RPM repositories (not ISO) on vanilla Centos 7.0.


Bravo! :)


Currently all Fuel system and deployment tests use ISO and we are
planning to re-implement all these jobs (including BVT, SWARM, and Fuel
CI jobs) to exclude ISO from the pipeline. That will allow us to get rid
of ISO as our deliverable and instead rely totally on package
repositories. Linux distributions like Ubuntu, Debian, RHEL, etc. are
already delivered via ISO/qcow2/etc. images and we'd better stop
reinventing a wheel and support our own ISO build code. That will allow
us to make Fuel admin node deployment more flexible.

I will infrom about our next steps here in the thread.


Thanks, Vova, this is an excellent step forward for ease-of-use with Fuel.

Nice work,
-jay

__
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] [fuel] mcollective configuration on slaves

[Vladimir Kozhukalov]

Currently we use /etc/nailgun-agent/nodiscover file to prevent early run of
nailgun-agent (and thus its conflict with cloud-init). We put this file
when we build an image [0] and then we remove this file at the late stage
of system start process when cloud-init is done [1]. Anyway this does not
look good and we'd better replace cloud-init with something else like
puppet and run this configuration during provisioning even before booting
into target operating system. Besides, running Puppet during provisioning
to do initial configuration will allow us to configure other services/files
in a consistent way. So, I prefer option #3. Let's write a spec for this.

[0]
https://github.com/openstack/fuel-agent/blob/master/fuel_agent/manager.py#L961
[1]
https://github.com/openstack/fuel-agent/blob/master/cloud-init-templates/boothook_fuel_9.0_ubuntu.jinja2#L91



Vladimir Kozhukalov

On Fri, Aug 12, 2016 at 8:29 AM, Georgy Kibardin 
wrote:

> Guys,
>
> Currently, at the time of the first boot Mcollective on slaves is
> configured by Cloud-init (host, port etc.) and by Nailgun agent when node
> identity is written. This happens in any order and already caused several
> problem which were fixed in bounds of https://bugs.launchpad.net/
> fuel/+bug/1455489. The last fix relies on hostname to figure that the
> provisioning is over and prevent Nailgun agent from messing with
> Mcollective. This solution is quite hacky and, I think, we need to come up
> with a better fix. So, the options are:
>
> 1. Do nothing
>   + No effort, no regression
>   - Existing solution is fragile and not simple enough to be sure that
> there are obviously no more bugs.
>   - Cloud-init does things on early boot stages which is a bit hard to
> debug.
>
> 2. "Manual" Mcollective configuration, triggered by Nailgun agent.
>   + Quite simple
>   - Not "cross-distro"
>   - Not consistent with the remaining configuration tasks (rewriting them
> worsens the problem above)
>
> 3. Use Puppet to configure Mcollective. (copy necessary input data into
> the chroot env and run puppet inside it)
>   + Using puppet is consistent with the way Fuel configures things
>   - It is not consistent with remaining configuration tasks, which is done
> via Cloud-init and moving them to Puppet takes some time.
>
> 4. Some other tool?
>
> New options, cons and pros are very welcome!
>
> Best,
> Georgy
>
> __
> 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-dev] [Fuel] Getting rid of ISO

[Vladimir Kozhukalov]

Dear colleagues,

We finally have working custom deployment job that deploys Fuel admin node
using online RPM repositories (not ISO) on vanilla Centos 7.0.

Currently all Fuel system and deployment tests use ISO and we are planning
to re-implement all these jobs (including BVT, SWARM, and Fuel CI jobs) to
exclude ISO from the pipeline. That will allow us to get rid of ISO as our
deliverable and instead rely totally on package repositories. Linux
distributions like Ubuntu, Debian, RHEL, etc. are already delivered via
ISO/qcow2/etc. images and we'd better stop reinventing a wheel and support
our own ISO build code. That will allow us to make Fuel admin node
deployment more flexible.

I will infrom about our next steps here in the thread.

Vladimir Kozhukalov
__
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] [fuel] mcollective configuration on slaves

[Georgy Kibardin]

Guys,

Currently, at the time of the first boot Mcollective on slaves is
configured by Cloud-init (host, port etc.) and by Nailgun agent when node
identity is written. This happens in any order and already caused several
problem which were fixed in bounds of
https://bugs.launchpad.net/fuel/+bug/1455489. The last fix relies on
hostname to figure that the provisioning is over and prevent Nailgun agent
from messing with Mcollective. This solution is quite hacky and, I think,
we need to come up with a better fix. So, the options are:

1. Do nothing
  + No effort, no regression
  - Existing solution is fragile and not simple enough to be sure that
there are obviously no more bugs.
  - Cloud-init does things on early boot stages which is a bit hard to
debug.

2. "Manual" Mcollective configuration, triggered by Nailgun agent.
  + Quite simple
  - Not "cross-distro"
  - Not consistent with the remaining configuration tasks (rewriting them
worsens the problem above)

3. Use Puppet to configure Mcollective. (copy necessary input data into the
chroot env and run puppet inside it)
  + Using puppet is consistent with the way Fuel configures things
  - It is not consistent with remaining configuration tasks, which is done
via Cloud-init and moving them to Puppet takes some time.

4. Some other tool?

New options, cons and pros are very welcome!

Best,
Georgy
__
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] [Fuel] Patches for python-fuelclient are blocked by broken master.python-fuelclient.pkgs.ubuntu.review_fuel_client

[Roman Prykhodchenko]

Folks,

It’s been several days when the entire python-fuelclient team is blocked by a 
broken CI job. Please make it non-voting ASAP.


- romcheg

> 8 серп. 2016 р. о 12:19 Roman Prykhodchenko  написав(ла):
> 
> Vladimir,
> 
> Thanks you for the update on this. Is there any ETA available?
> 
> On Mon, Aug 8, 2016 at 12:09 PM Vladimir Kozhukalov  > wrote:
> We are working on this. Will fix soon.
> 
> Vladimir Kozhukalov
> 
> On Mon, Aug 8, 2016 at 12:52 PM, Roman Prykhodchenko  > wrote:
> If it’s not possible to fix this job during next few hours, let’s mark in as 
> non-voting until the bug(s) are fixed.
> 
> > 8 серп. 2016 р. о 11:48 Roman Prykhodchenko  > > написав(ла):
> >
> > Folks,
> >
> > Since the end of last week 
> > master.python-fuelclient.pkgs.ubuntu.review_fuel_client [1] blocks all 
> > patches to python-fuelclient. As logs suggest this issue is caused by the 
> > Xenial merge party.
> >
> > Please resolve the issue ASAP because some folks are blocked and cannot 
> > finish their jobs in time.
> >
> >
> > 1. 
> > https://ci.fuel-infra.org/job/master.python-fuelclient.pkgs.ubuntu.review_fuel_client/
> >  
> > 
> >
> > - romcheg
> >
> >
> >
> 
> 
> __
> 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 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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] [Fuel] Patches for python-fuelclient are blocked by broken master.python-fuelclient.pkgs.ubuntu.review_fuel_client

[Roman Prykhodchenko]

Vladimir,

Thanks you for the update on this. Is there any ETA available?

On Mon, Aug 8, 2016 at 12:09 PM Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:

> We are working on this. Will fix soon.
>
> Vladimir Kozhukalov
>
> On Mon, Aug 8, 2016 at 12:52 PM, Roman Prykhodchenko 
> wrote:
>
>> If it’s not possible to fix this job during next few hours, let’s mark in
>> as non-voting until the bug(s) are fixed.
>>
>> > 8 серп. 2016 р. о 11:48 Roman Prykhodchenko 
>> написав(ла):
>> >
>> > Folks,
>> >
>> > Since the end of last week
>> master.python-fuelclient.pkgs.ubuntu.review_fuel_client [1] blocks all
>> patches to python-fuelclient. As logs suggest this issue is caused by the
>> Xenial merge party.
>> >
>> > Please resolve the issue ASAP because some folks are blocked and cannot
>> finish their jobs in time.
>> >
>> >
>> > 1.
>> https://ci.fuel-infra.org/job/master.python-fuelclient.pkgs.ubuntu.review_fuel_client/
>> >
>> > - romcheg
>> >
>> >
>> >
>>
>>
>> __
>> 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

Re: [openstack-dev] [Fuel] Patches for python-fuelclient are blocked by broken master.python-fuelclient.pkgs.ubuntu.review_fuel_client

[Vladimir Kozhukalov]

We are working on this. Will fix soon.

Vladimir Kozhukalov

On Mon, Aug 8, 2016 at 12:52 PM, Roman Prykhodchenko  wrote:

> If it’s not possible to fix this job during next few hours, let’s mark in
> as non-voting until the bug(s) are fixed.
>
> > 8 серп. 2016 р. о 11:48 Roman Prykhodchenko  написав(ла):
> >
> > Folks,
> >
> > Since the end of last week 
> > master.python-fuelclient.pkgs.ubuntu.review_fuel_client
> [1] blocks all patches to python-fuelclient. As logs suggest this issue is
> caused by the Xenial merge party.
> >
> > Please resolve the issue ASAP because some folks are blocked and cannot
> finish their jobs in time.
> >
> >
> > 1. https://ci.fuel-infra.org/job/master.python-fuelclient.pkgs.
> ubuntu.review_fuel_client/
> >
> > - romcheg
> >
> >
> >
>
>
> __
> 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] [Fuel] Patches for python-fuelclient are blocked by broken master.python-fuelclient.pkgs.ubuntu.review_fuel_client

[Roman Prykhodchenko]

If it’s not possible to fix this job during next few hours, let’s mark in as 
non-voting until the bug(s) are fixed.

> 8 серп. 2016 р. о 11:48 Roman Prykhodchenko  написав(ла):
> 
> Folks,
> 
> Since the end of last week 
> master.python-fuelclient.pkgs.ubuntu.review_fuel_client [1] blocks all 
> patches to python-fuelclient. As logs suggest this issue is caused by the 
> Xenial merge party.
> 
> Please resolve the issue ASAP because some folks are blocked and cannot 
> finish their jobs in time.
> 
> 
> 1. 
> https://ci.fuel-infra.org/job/master.python-fuelclient.pkgs.ubuntu.review_fuel_client/
> 
> - romcheg
> 
> 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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] [Fuel] Patches for python-fuelclient are blocked by broken master.python-fuelclient.pkgs.ubuntu.review_fuel_client

[Roman Prykhodchenko]

Folks,

Since the end of last week 
master.python-fuelclient.pkgs.ubuntu.review_fuel_client [1] blocks all patches 
to python-fuelclient. As logs suggest this issue is caused by the Xenial merge 
party.

Please resolve the issue ASAP because some folks are blocked and cannot finish 
their jobs in time.


1. 
https://ci.fuel-infra.org/job/master.python-fuelclient.pkgs.ubuntu.review_fuel_client/

- romcheg





signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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] [Fuel] New version of fuel-devops (2.9.23)

[Alexey Stepanov]

Hi all!
In the nearest future we are going to update the 'fuel-devops' framework on
our CI to the version 2.9.23.
It's bugfix-only version. As was written before, no new development is
planned for this thread.

Changes since 2.9.22:

- fix  *AddressPool._safe_create_network* method [1]

List of all changes is available on github [2].

[1] https://review.openstack.org/#/c/350400/
[2] https://github.com/openstack/fuel-devops/compare/2.9.22...release/2.9

-- 
Best regards,
Alexey Stepanov
__
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] [Fuel]Nominating Vitalii Kulanov for python-fuelclient-core

[Sergii Golovatiuk]

Congratulations Vitalii!

--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser

On Mon, Aug 1, 2016 at 11:54 AM, Roman Prykhodchenko  wrote:

> The entire core team has voted for the nomination so I’m putting it to
> power. Let’s all welcome Vitalii as a new core reviewer. Congratulations!
>
> 1 серп. 2016 р. о 08:55 Aleksey Kasatkin 
> написав(ла):
>
> +1
>
>
> Aleksey Kasatkin
>
>
> On Mon, Jul 25, 2016 at 7:46 PM, Igor Kalnitsky 
> wrote:
>
>> Vitaly's doing a great job. +2, no doubts!
>>
>> On Mon, Jul 25, 2016 at 6:27 PM, Tatyana Leontovich
>>  wrote:
>> > A huge +1
>> >
>> > On Mon, Jul 25, 2016 at 4:33 PM, Yegor Kotko 
>> wrote:
>> >>
>> >> +1
>> >>
>> >> On Mon, Jul 25, 2016 at 3:19 PM, Roman Prykhodchenko 
>> >> wrote:
>> >>>
>> >>> Hi Fuelers,
>> >>>
>> >>> Vitalii has been providing great code reviews and patches for some
>> time.
>> >>> His recent commitment to help consolidating both old and new fuel
>> clients
>> >>> and his bug-squashing activities show his willingness to step up and
>> take
>> >>> responsibilities within the community. He can often be found in #fuel
>> as
>> >>> vkulanov.
>> >>>
>> >>>
>> >>>
>> http://stackalytics.com/?module=python-fuelclient_id=vitaliy-t=mitaka
>> >>> http://stackalytics.com/?module=python-fuelclient_id=vitaliy-t
>> >>>
>> >>>
>> >>> P. S. Sorry for sending this email twice — I realized I didn’t put a
>> >>> topic to the subject.
>> >>>
>> >>>
>> >>> - romcheg
>> >>>
>> >>>
>> >>>
>> __
>> >>> 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
>> >
>>
>> __
>> 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
>
>
__
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] [Fuel]Nominating Vitalii Kulanov for python-fuelclient-core

[Roman Prykhodchenko]

The entire core team has voted for the nomination so I’m putting it to power. 
Let’s all welcome Vitalii as a new core reviewer. Congratulations!

> 1 серп. 2016 р. о 08:55 Aleksey Kasatkin  написав(ла):
> 
> +1
> 
> 
> Aleksey Kasatkin
> 
> 
> On Mon, Jul 25, 2016 at 7:46 PM, Igor Kalnitsky  > wrote:
> Vitaly's doing a great job. +2, no doubts!
> 
> On Mon, Jul 25, 2016 at 6:27 PM, Tatyana Leontovich
> > wrote:
> > A huge +1
> >
> > On Mon, Jul 25, 2016 at 4:33 PM, Yegor Kotko  > > wrote:
> >>
> >> +1
> >>
> >> On Mon, Jul 25, 2016 at 3:19 PM, Roman Prykhodchenko  >> >
> >> wrote:
> >>>
> >>> Hi Fuelers,
> >>>
> >>> Vitalii has been providing great code reviews and patches for some time.
> >>> His recent commitment to help consolidating both old and new fuel clients
> >>> and his bug-squashing activities show his willingness to step up and take
> >>> responsibilities within the community. He can often be found in #fuel as
> >>> vkulanov.
> >>>
> >>>
> >>> http://stackalytics.com/?module=python-fuelclient_id=vitaliy-t=mitaka
> >>>  
> >>> 
> >>> http://stackalytics.com/?module=python-fuelclient_id=vitaliy-t 
> >>> 
> >>>
> >>>
> >>> P. S. Sorry for sending this email twice — I realized I didn’t put a
> >>> topic to the subject.
> >>>
> >>>
> >>> - romcheg
> >>>
> >>>
> >>> __
> >>> 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 
> > 
> >
> 
> __
> 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



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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] [Fuel]Nominating Vitalii Kulanov for python-fuelclient-core

[Aleksey Kasatkin]

+1


Aleksey Kasatkin


On Mon, Jul 25, 2016 at 7:46 PM, Igor Kalnitsky 
wrote:

> Vitaly's doing a great job. +2, no doubts!
>
> On Mon, Jul 25, 2016 at 6:27 PM, Tatyana Leontovich
>  wrote:
> > A huge +1
> >
> > On Mon, Jul 25, 2016 at 4:33 PM, Yegor Kotko 
> wrote:
> >>
> >> +1
> >>
> >> On Mon, Jul 25, 2016 at 3:19 PM, Roman Prykhodchenko 
> >> wrote:
> >>>
> >>> Hi Fuelers,
> >>>
> >>> Vitalii has been providing great code reviews and patches for some
> time.
> >>> His recent commitment to help consolidating both old and new fuel
> clients
> >>> and his bug-squashing activities show his willingness to step up and
> take
> >>> responsibilities within the community. He can often be found in #fuel
> as
> >>> vkulanov.
> >>>
> >>>
> >>>
> http://stackalytics.com/?module=python-fuelclient_id=vitaliy-t=mitaka
> >>> http://stackalytics.com/?module=python-fuelclient_id=vitaliy-t
> >>>
> >>>
> >>> P. S. Sorry for sending this email twice — I realized I didn’t put a
> >>> topic to the subject.
> >>>
> >>>
> >>> - romcheg
> >>>
> >>>
> >>>
> __
> >>> 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
> >
>
> __
> 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-dev] [fuel] Meeting for today 7/28 is caneled

[Andrew Woodward]

The meeting agenda is empty for this week's meeting is empty so I'm calling
it on the meeting.

https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
-- 

--

Andrew Woodward

Mirantis

Fuel Community Ambassador

Ceph Community
__
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] [fuel] Capacity table

[Vitaly Kramskikh]

If "new design" is the design you've proposed in the original email, then
no - we'll have to reopen the bug and then revert the change again.

2016-07-27 11:36 GMT+03:00 Dmitry Dmitriev :

> Hello Vitaly,
>
> Thank you for this answer.
> The main question here is the business logic.
> Do we have to use new design or don’t.
>
> With best regards, Dmitry
>
> On 26 Jul 2016, at 17:47, Vitaly Kramskikh 
> wrote:
>
> Hi, Dmitry,
>
> Your design seems to be similar to one of our attempts to fix this bug:
> https://review.openstack.org/#/c/280737/. Though this fix was reverted,
> because it led to the bug with a higher priority:
> https://bugs.launchpad.net/fuel/+bug/1556909. So your proposed design
> would lead to reopening of this bug.
>
> 2016-07-19 11:06 GMT+03:00 Dmitry Dmitriev :
>
>> Hello All!
>>
>> We have a very old bug about the Capacity table on the Dashboard tab of
>> environment in Fuel:
>>
>> https://bugs.launchpad.net/fuel/+bug/1375750
>>
>> Current design:
>>
>> https://drive.google.com/open?id=0Bxi_JFs365mBNy1WT0xQT253SWc
>>
>> It shows the full capacity (CPU/Memory/HDD) of all discovered by Fuel
>> nodes.
>>
>> New design:
>>
>> https://drive.google.com/open?id=0Bxi_JFs365mBaWZ0cUtla3N6aEU
>>
>> It contains compute node CPU/Memory capacity and Ceph disk capacity only.
>>
>> New design pros:
>> - cloud administrator can easily estimate all available resources for
>> cloud instances
>>
>> New design cons:
>> - if cloud doesn’t use Ceph then HDD value is zero
>>
>> What do you think about the new design?
>>
>> With best regards, Dmitry
>>
>>
>
>
> --
> Vitaly Kramskikh,
> Fuel UI Tech Lead,
> Mirantis, Inc.
>
>
>


-- 
Vitaly Kramskikh,
Fuel UI Tech Lead,
Mirantis, Inc.
__
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] [fuel] Capacity table

[Dmitry Dmitriev]

Hello Vitaly,

Thank you for this answer.
The main question here is the business logic.
Do we have to use new design or don’t.

With best regards, Dmitry

> On 26 Jul 2016, at 17:47, Vitaly Kramskikh  wrote:
> 
> Hi, Dmitry,
> 
> Your design seems to be similar to one of our attempts to fix this bug: 
> https://review.openstack.org/#/c/280737/ 
> . Though this fix was reverted, 
> because it led to the bug with a higher priority: 
> https://bugs.launchpad.net/fuel/+bug/1556909 
> . So your proposed design would 
> lead to reopening of this bug.
> 
> 2016-07-19 11:06 GMT+03:00 Dmitry Dmitriev  >:
> Hello All!
> 
> We have a very old bug about the Capacity table on the Dashboard tab of 
> environment in Fuel:
> 
> https://bugs.launchpad.net/fuel/+bug/1375750 
> 
> 
> Current design:
> 
> https://drive.google.com/open?id=0Bxi_JFs365mBNy1WT0xQT253SWc 
> 
> 
> It shows the full capacity (CPU/Memory/HDD) of all discovered by Fuel nodes.
> 
> New design: 
> 
> https://drive.google.com/open?id=0Bxi_JFs365mBaWZ0cUtla3N6aEU 
> 
> 
> It contains compute node CPU/Memory capacity and Ceph disk capacity only.
> 
> New design pros:
> - cloud administrator can easily estimate all available resources for cloud 
> instances
> 
> New design cons:
> - if cloud doesn’t use Ceph then HDD value is zero
> 
> What do you think about the new design?
> 
> With best regards, Dmitry
> 
> 
> 
> 
> -- 
> Vitaly Kramskikh,
> Fuel UI Tech Lead,
> Mirantis, Inc.

__
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] [fuel] Capacity table

[Vitaly Kramskikh]

Hi, Dmitry,

Your design seems to be similar to one of our attempts to fix this bug:
https://review.openstack.org/#/c/280737/. Though this fix was reverted,
because it led to the bug with a higher priority:
https://bugs.launchpad.net/fuel/+bug/1556909. So your proposed design would
lead to reopening of this bug.

2016-07-19 11:06 GMT+03:00 Dmitry Dmitriev :

> Hello All!
>
> We have a very old bug about the Capacity table on the Dashboard tab of
> environment in Fuel:
>
> https://bugs.launchpad.net/fuel/+bug/1375750
>
> Current design:
>
> https://drive.google.com/open?id=0Bxi_JFs365mBNy1WT0xQT253SWc
>
> It shows the full capacity (CPU/Memory/HDD) of all discovered by Fuel
> nodes.
>
> New design:
>
> https://drive.google.com/open?id=0Bxi_JFs365mBaWZ0cUtla3N6aEU
>
> It contains compute node CPU/Memory capacity and Ceph disk capacity only.
>
> New design pros:
> - cloud administrator can easily estimate all available resources for
> cloud instances
>
> New design cons:
> - if cloud doesn’t use Ceph then HDD value is zero
>
> What do you think about the new design?
>
> With best regards, Dmitry
>
>


-- 
Vitaly Kramskikh,
Fuel UI Tech Lead,
Mirantis, Inc.
__
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] [Fuel]Nominating Vitalii Kulanov for python-fuelclient-core

[Igor Kalnitsky]

Vitaly's doing a great job. +2, no doubts!

On Mon, Jul 25, 2016 at 6:27 PM, Tatyana Leontovich
 wrote:
> A huge +1
>
> On Mon, Jul 25, 2016 at 4:33 PM, Yegor Kotko  wrote:
>>
>> +1
>>
>> On Mon, Jul 25, 2016 at 3:19 PM, Roman Prykhodchenko 
>> wrote:
>>>
>>> Hi Fuelers,
>>>
>>> Vitalii has been providing great code reviews and patches for some time.
>>> His recent commitment to help consolidating both old and new fuel clients
>>> and his bug-squashing activities show his willingness to step up and take
>>> responsibilities within the community. He can often be found in #fuel as
>>> vkulanov.
>>>
>>>
>>> http://stackalytics.com/?module=python-fuelclient_id=vitaliy-t=mitaka
>>> http://stackalytics.com/?module=python-fuelclient_id=vitaliy-t
>>>
>>>
>>> P. S. Sorry for sending this email twice — I realized I didn’t put a
>>> topic to the subject.
>>>
>>>
>>> - romcheg
>>>
>>>
>>> __
>>> 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
>

__
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] [Fuel]Nominating Vitalii Kulanov for python-fuelclient-core

[Tatyana Leontovich]

A huge +1

On Mon, Jul 25, 2016 at 4:33 PM, Yegor Kotko  wrote:

> +1
>
> On Mon, Jul 25, 2016 at 3:19 PM, Roman Prykhodchenko 
> wrote:
>
>> Hi Fuelers,
>>
>> Vitalii has been providing great code reviews and patches for some time.
>> His recent commitment to help consolidating both old and new fuel clients
>> and his bug-squashing activities show his willingness to step up and take
>> responsibilities within the community. He can often be found in #fuel as
>> vkulanov.
>>
>>
>> http://stackalytics.com/?module=python-fuelclient_id=vitaliy-t=mitaka
>> http://stackalytics.com/?module=python-fuelclient_id=vitaliy-t
>>
>>
>> P. S. Sorry for sending this email twice — I realized I didn’t put a
>> topic to the subject.
>>
>>
>> - romcheg
>>
>> __
>> 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

Re: [openstack-dev] [Fuel]Nominating Vitalii Kulanov for python-fuelclient-core

[Yegor Kotko]

+1

On Mon, Jul 25, 2016 at 3:19 PM, Roman Prykhodchenko  wrote:

> Hi Fuelers,
>
> Vitalii has been providing great code reviews and patches for some time.
> His recent commitment to help consolidating both old and new fuel clients
> and his bug-squashing activities show his willingness to step up and take
> responsibilities within the community. He can often be found in #fuel as
> vkulanov.
>
>
> http://stackalytics.com/?module=python-fuelclient_id=vitaliy-t=mitaka
> http://stackalytics.com/?module=python-fuelclient_id=vitaliy-t
>
>
> P. S. Sorry for sending this email twice — I realized I didn’t put a topic
> to the subject.
>
>
> - romcheg
>
> __
> 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-dev] [Fuel]Nominating Vitalii Kulanov for python-fuelclient-core

[Roman Prykhodchenko]

Hi Fuelers,

Vitalii has been providing great code reviews and patches for some time. His 
recent commitment to help consolidating both old and new fuel clients and his 
bug-squashing activities show his willingness to step up and take 
responsibilities within the community. He can often be found in #fuel as 
vkulanov.

http://stackalytics.com/?module=python-fuelclient_id=vitaliy-t=mitaka
http://stackalytics.com/?module=python-fuelclient_id=vitaliy-t


P. S. Sorry for sending this email twice — I realized I didn’t put a topic to 
the subject.


- romcheg


signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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] [Fuel] New version of fuel-devops (2.9.22)

[Alexey Stepanov]

Hi All!

Today we are going to update the 'fuel-devops' framework on our product CI
to the version 2.9.22.
It's the FINAL version in 2.9 thread, new active development will be
produced in 3.x thread only, and 3.0.1 is released as first of it's.

Changes sinse 2.9.21:
* For devops:

  - paramiko 2.0.1 is banned due to connection failures has been
reproduced.  [1]
  - do not log keystoneauth1 debug info -- logs will be more readable.  [2]
  - fixed bug, when unexpected 'k e y s' header has been printed on 'dos.py
list' request, if not any environments registered in database.  [3]

* For QA automation:

  - SSHClient().check_call() now receives error_info optional parameter as
header for error log.  [4]
  - ExecResult class is implemented as universal storage for execution
results. R/W access for 'stdout', 'stderr' and 'exit_code'. R/O access to
UNICODE 'stdout_str', 'stderr_str' and 'others'. On-demand decode stdout as
JSON or YAML.  [5]
  - Support for chrony NTP has been ported from fuel-devops 3.  [6]
  - Implemented Subprocess helper class with SSHClient-like API for calling
subprocess lock-free (buffers polled every 100 ms). [7]
  - On SSHClient request from cache, catch all exceptions as a reason for
reconnect. [8]


List of all changes is available on github [9].

[1] https://review.openstack.org/#/c/344746/
[2] https://review.openstack.org/#/c/345377/
[3] https://review.openstack.org/#/c/345991/
[4] https://review.openstack.org/#/c/340996/
[5] https://review.openstack.org/#/c/340997/
[6] https://review.openstack.org/#/c/342101/
[7] https://review.openstack.org/#/c/342712/
[8] https://review.openstack.org/#/c/344667/
[9] https://github.com/openstack/fuel-devops/compare/2.9.21...release/2.9


-- 
Best regards,
Alexey Stepanov
__
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] [fuel] Fuel meeting Canceled

[Andrew Woodward]

Again the agenda [1] is empty again so I'm calling it on the meeting this
week.

[1] https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
-- 

--

Andrew Woodward

Mirantis

Fuel Community Ambassador

Ceph Community
__
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] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Tatyana Leontovich]

Alexey,
Congrats!




On Thu, Jul 21, 2016 at 3:08 PM, Dennis Dmitriev 
wrote:

> +1
>
>
> On 07/21/2016 01:56 PM, Alexander Kurenyshev wrote:
>
> +1
>
> On Wed, Jul 20, 2016 at 10:47 AM, Vladimir Khlyunev <
> vkhlyu...@mirantis.com> wrote:
>
>> +1
>>
>> On Mon, Jul 18, 2016 at 3:14 PM, Dmitry Tyzhnenko <
>> dtyzhne...@mirantis.com> wrote:
>>
>>> +1
>>>
>>> On Fri, Jul 15, 2016 at 4:41 PM, Artem Panchenko <
>>> apanche...@mirantis.com> wrote:
>>>
 +1


 On 15.07.16 16:25, Tatyana Leontovich wrote:

 +1

 On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova <
 aurlap...@mirantis.com> wrote:

> +1
>
> On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy <
> asledzins...@mirantis.com> wrote:
>
>> Hi,
>> I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops
>> [1] core.
>>
>> Alexey is doing great job improving fuel-qa and fuel-devops projects.
>> He's become an expert in code base in very short terms so I think he
>> deserves to be a part of fuel-qa/fuel-devops core team.
>>
>> Please, vote for Alexey!
>>
>> [0]
>> 
>> http://stackalytics.com/?release=all=fuel-qa_id=astepanov-m=marks
>> [1]
>> 
>> http://stackalytics.com/?release=all=fuel-devops_id=astepanov-m=marks
>>
>> --
>> Thanks,
>> Andrey Sledzinskiy
>> QA Engineer,
>> Mirantis, Kharkiv
>>
>>
>> __
>> 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:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 --
 Artem Panchenko
 QA Engineer



 __
 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


>>>
>>>
>>> --
>>> WBR,
>>> Dmitry T.
>>> Fuel QA Engineer
>>> http://www.mirantis.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
>>>
>>>
>>
>>
>> --
>> Best regards,
>> Vladimir Khlyunev
>> QA engineer,
>> Mirantis Inc.
>>
>> __
>> 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
>>
>>
>
>
> --
> Best Regards,
>
> Alex
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> --
> Regards,
> Dennis Dmitriev
> QA Engineer,
> Mirantis Inc. http://www.mirantis.com
> e-mail/jabber: dis.x...@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: 

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Dennis Dmitriev]

+1

On 07/21/2016 01:56 PM, Alexander Kurenyshev wrote:
> +1
>
> On Wed, Jul 20, 2016 at 10:47 AM, Vladimir Khlyunev
> > wrote:
>
> +1
>
> On Mon, Jul 18, 2016 at 3:14 PM, Dmitry Tyzhnenko
> > wrote:
>
> +1
>
> On Fri, Jul 15, 2016 at 4:41 PM, Artem Panchenko
> > wrote:
>
> +1
>
>
> On 15.07.16 16:25, Tatyana Leontovich wrote:
>> +1
>>
>> On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova
>> >
>> wrote:
>>
>> +1
>>
>> On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy
>> > > wrote:
>>
>> Hi,
>> I'd like to nominate Alexey Stepanovfor fuel-qa
>> [0] and fuel-devops [1] core.
>>
>> Alexey is doing great job improving fuel-qa and
>> fuel-devops projects.
>> He's become an expert in code base in very short
>> terms so I think he deserves to be a part of
>> fuel-qa/fuel-devops core team. 
>>
>> Please, vote for Alexey!
>>
>> [0]
>> 
>> http://stackalytics.com/?release=all=fuel-qa_id=astepanov-m=marks
>>
>> [1]
>> 
>> http://stackalytics.com/?release=all=fuel-devops_id=astepanov-m=marks
>>
>>
>> -- 
>> Thanks,
>> Andrey Sledzinskiy 
>> QA Engineer,
>> Mirantis, Kharkiv
>>
>> 
>> __
>> 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
>
> -- 
> Artem Panchenko
> QA Engineer
>
>
> 
> __
> 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
>
>
>
>
> -- 
> WBR,
> Dmitry T.
> Fuel QA Engineer
> http://www.mirantis.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
>
>
>
>
> -- 
> Best regards,
> Vladimir Khlyunev
> QA engineer,
> Mirantis Inc.
>
> __
> 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
>
>
>
>
> -- 
> Best Regards,
>
> Alex
>
>
> 

Re: [openstack-dev] [fuel-octane] Nominate Sergey Abramov to fuel-octane core

[Yuriy Taraday]

+1 We need more cores anyway ;)

On Thu, Jul 21, 2016 at 11:56 AM Oleg Gelbukh  wrote:

> +1 here
>
> Sergey's performance and quality of the code he submitted are impressive.
> Please, keep going.
>
> --
> Best regards,
> Oleg Gelbukh
>
> On Thu, Jul 21, 2016 at 10:21 AM, Artur Svechnikov <
> asvechni...@mirantis.com> wrote:
>
>> +1
>>
>> Best regards,
>> Svechnikov Artur
>>
>> On Thu, Jul 21, 2016 at 12:10 AM, Ilya Kharin 
>> wrote:
>>
>>> Hello,
>>>
>>> I would like to nominate Sergey Abramov to fuel-octane core due to his
>>> significant contribution to the project [1] and [2].
>>>
>>> Best regards,
>>> Ilya Kharin.
>>>
>>> [1] http://stackalytics.com/report/contribution/fuel-octane/90
>>> [2]
>>> http://stackalytics.com/?release=all=fuel-octane=marks_id=sabramov
>>>
>>>
>>> __
>>> 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
>
__
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] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Alexander Kurenyshev]

+1

On Wed, Jul 20, 2016 at 10:47 AM, Vladimir Khlyunev 
wrote:

> +1
>
> On Mon, Jul 18, 2016 at 3:14 PM, Dmitry Tyzhnenko  > wrote:
>
>> +1
>>
>> On Fri, Jul 15, 2016 at 4:41 PM, Artem Panchenko > > wrote:
>>
>>> +1
>>>
>>>
>>> On 15.07.16 16:25, Tatyana Leontovich wrote:
>>>
>>> +1
>>>
>>> On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova <
>>> aurlap...@mirantis.com> wrote:
>>>
 +1

 On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy <
 asledzins...@mirantis.com> wrote:

> Hi,
> I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops
> [1] core.
>
> Alexey is doing great job improving fuel-qa and fuel-devops projects.
> He's become an expert in code base in very short terms so I think he
> deserves to be a part of fuel-qa/fuel-devops core team.
>
> Please, vote for Alexey!
>
> [0]
> http://stackalytics.com/?release=all=fuel-qa_id=astepanov-m=marks
> [1]
> http://stackalytics.com/?release=all=fuel-devops_id=astepanov-m=marks
>
> --
> Thanks,
> Andrey Sledzinskiy
> QA Engineer,
> Mirantis, Kharkiv
>
>
> __
> 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:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>> --
>>> Artem Panchenko
>>> QA Engineer
>>>
>>>
>>>
>>> __
>>> 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
>>>
>>>
>>
>>
>> --
>> WBR,
>> Dmitry T.
>> Fuel QA Engineer
>> http://www.mirantis.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
>>
>>
>
>
> --
> Best regards,
> Vladimir Khlyunev
> QA engineer,
> Mirantis Inc.
>
> __
> 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
>
>


-- 
Best Regards,

Alex
__
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] [fuel-octane] Nominate Sergey Abramov to fuel-octane core

[Oleg Gelbukh]

+1 here

Sergey's performance and quality of the code he submitted are impressive.
Please, keep going.

--
Best regards,
Oleg Gelbukh

On Thu, Jul 21, 2016 at 10:21 AM, Artur Svechnikov  wrote:

> +1
>
> Best regards,
> Svechnikov Artur
>
> On Thu, Jul 21, 2016 at 12:10 AM, Ilya Kharin 
> wrote:
>
>> Hello,
>>
>> I would like to nominate Sergey Abramov to fuel-octane core due to his
>> significant contribution to the project [1] and [2].
>>
>> Best regards,
>> Ilya Kharin.
>>
>> [1] http://stackalytics.com/report/contribution/fuel-octane/90
>> [2]
>> http://stackalytics.com/?release=all=fuel-octane=marks_id=sabramov
>>
>> __
>> 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

Re: [openstack-dev] [fuel-octane] Nominate Sergey Abramov to fuel-octane core

[Artur Svechnikov]

+1

Best regards,
Svechnikov Artur

On Thu, Jul 21, 2016 at 12:10 AM, Ilya Kharin  wrote:

> Hello,
>
> I would like to nominate Sergey Abramov to fuel-octane core due to his
> significant contribution to the project [1] and [2].
>
> Best regards,
> Ilya Kharin.
>
> [1] http://stackalytics.com/report/contribution/fuel-octane/90
> [2]
> http://stackalytics.com/?release=all=fuel-octane=marks_id=sabramov
>
> __
> 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-dev] [fuel-octane] Nominate Sergey Abramov to fuel-octane core

[Ilya Kharin]

Hello,

I would like to nominate Sergey Abramov to fuel-octane core due to his
significant contribution to the project [1] and [2].

Best regards,
Ilya Kharin.

[1] http://stackalytics.com/report/contribution/fuel-octane/90
[2]
http://stackalytics.com/?release=all=fuel-octane=marks_id=sabramov
__
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] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Vladimir Khlyunev]

+1

On Mon, Jul 18, 2016 at 3:14 PM, Dmitry Tyzhnenko 
wrote:

> +1
>
> On Fri, Jul 15, 2016 at 4:41 PM, Artem Panchenko 
> wrote:
>
>> +1
>>
>>
>> On 15.07.16 16:25, Tatyana Leontovich wrote:
>>
>> +1
>>
>> On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova <
>> aurlap...@mirantis.com> wrote:
>>
>>> +1
>>>
>>> On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy <
>>> asledzins...@mirantis.com> wrote:
>>>
 Hi,
 I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops
 [1] core.

 Alexey is doing great job improving fuel-qa and fuel-devops projects.
 He's become an expert in code base in very short terms so I think he
 deserves to be a part of fuel-qa/fuel-devops core team.

 Please, vote for Alexey!

 [0]
 http://stackalytics.com/?release=all=fuel-qa_id=astepanov-m=marks
 [1]
 http://stackalytics.com/?release=all=fuel-devops_id=astepanov-m=marks

 --
 Thanks,
 Andrey Sledzinskiy
 QA Engineer,
 Mirantis, Kharkiv


 __
 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:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> --
>> Artem Panchenko
>> QA Engineer
>>
>>
>> __
>> 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
>>
>>
>
>
> --
> WBR,
> Dmitry T.
> Fuel QA Engineer
> http://www.mirantis.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
>
>


-- 
Best regards,
Vladimir Khlyunev
QA engineer,
Mirantis Inc.
__
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] [fuel] Capacity table

[Dmitry Dmitriev]

Hello All!

We have a very old bug about the Capacity table on the Dashboard tab of 
environment in Fuel:

https://bugs.launchpad.net/fuel/+bug/1375750 


Current design:

https://drive.google.com/open?id=0Bxi_JFs365mBNy1WT0xQT253SWc

It shows the full capacity (CPU/Memory/HDD) of all discovered by Fuel nodes.

New design: 

https://drive.google.com/open?id=0Bxi_JFs365mBaWZ0cUtla3N6aEU

It contains compute node CPU/Memory capacity and Ceph disk capacity only.

New design pros:
- cloud administrator can easily estimate all available resources for cloud 
instances

New design cons:
- if cloud doesn’t use Ceph then HDD value is zero

What do you think about the new design?

With best regards, Dmitry

__
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] [fuel documentation] new cores in fuel-docs-core

[Evgeny Konstantinov]

Hey everyone,

We've added new cores to the Fuel documentation project:

https://review.openstack.org/#/admin/groups/657,members

Thew new cores are:

Olena Logvinova
Mariia Zlatkova

Over the past ~1,5 years they've contributed a lot of quality docs pieces
to various openstack projects, including Fuel docs.

We've also removed inactive members.

Please let me know if you have concerns etc.

-- 
Evgeny
Technical Writer
email: evko...@mirantis.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

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Dmitry Tyzhnenko]

+1

On Fri, Jul 15, 2016 at 4:41 PM, Artem Panchenko 
wrote:

> +1
>
>
> On 15.07.16 16:25, Tatyana Leontovich wrote:
>
> +1
>
> On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova <
> aurlap...@mirantis.com> wrote:
>
>> +1
>>
>> On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy <
>> asledzins...@mirantis.com> wrote:
>>
>>> Hi,
>>> I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops
>>> [1] core.
>>>
>>> Alexey is doing great job improving fuel-qa and fuel-devops projects.
>>> He's become an expert in code base in very short terms so I think he
>>> deserves to be a part of fuel-qa/fuel-devops core team.
>>>
>>> Please, vote for Alexey!
>>>
>>> [0]
>>> http://stackalytics.com/?release=all=fuel-qa_id=astepanov-m=marks
>>> [1]
>>> http://stackalytics.com/?release=all=fuel-devops_id=astepanov-m=marks
>>>
>>> --
>>> Thanks,
>>> Andrey Sledzinskiy
>>> QA Engineer,
>>> Mirantis, Kharkiv
>>>
>>>
>>> __
>>> 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:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> --
> Artem Panchenko
> QA Engineer
>
>
> __
> 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
>
>


-- 
WBR,
Dmitry T.
Fuel QA Engineer
http://www.mirantis.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

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Artem Panchenko]

+1

On 15.07.16 16:25, Tatyana Leontovich wrote:

+1

On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova 
> wrote:


+1

On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy
> wrote:

Hi,
I'd like to nominate Alexey Stepanovfor fuel-qa [0] and
fuel-devops [1] core.

Alexey is doing great job improving fuel-qa and fuel-devops
projects.
He's become an expert in code base in very short terms so I
think he deserves to be a part of fuel-qa/fuel-devops core team.

Please, vote for Alexey!

[0]

http://stackalytics.com/?release=all=fuel-qa_id=astepanov-m=marks

[1]

http://stackalytics.com/?release=all=fuel-devops_id=astepanov-m=marks


-- 
Thanks,

Andrey Sledzinskiy
QA Engineer,
Mirantis, Kharkiv


__
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


--
Artem Panchenko
QA Engineer

__
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] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Tatyana Leontovich]

+1

On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova 
wrote:

> +1
>
> On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy <
> asledzins...@mirantis.com> wrote:
>
>> Hi,
>> I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops [1]
>> core.
>>
>> Alexey is doing great job improving fuel-qa and fuel-devops projects.
>> He's become an expert in code base in very short terms so I think he
>> deserves to be a part of fuel-qa/fuel-devops core team.
>>
>> Please, vote for Alexey!
>>
>> [0]
>> http://stackalytics.com/?release=all=fuel-qa_id=astepanov-m=marks
>> [1]
>> http://stackalytics.com/?release=all=fuel-devops_id=astepanov-m=marks
>>
>> --
>> Thanks,
>> Andrey Sledzinskiy
>> QA Engineer,
>> Mirantis, Kharkiv
>>
>> __
>> 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

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Bulat Gaifullin]

+1

Regards,
Bulat Gaifullin
Mirantis Inc.



> On 15 Jul 2016, at 16:08, Anastasia Urlapova  wrote:
> 
> +1
> 
> On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy 
> > wrote:
> Hi,
> I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops [1] core.
> 
> Alexey is doing great job improving fuel-qa and fuel-devops projects. 
> He's become an expert in code base in very short terms so I think he deserves 
> to be a part of fuel-qa/fuel-devops core team.  
> 
> Please, vote for Alexey!
> 
> [0] 
> http://stackalytics.com/?release=all=fuel-qa_id=astepanov-m=marks
>  
> 
> [1] 
> http://stackalytics.com/?release=all=fuel-devops_id=astepanov-m=marks
>  
> 
> 
> -- 
> Thanks, 
> Andrey Sledzinskiy  
> QA Engineer, 
> Mirantis, Kharkiv
> 
> __
> 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

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Anastasia Urlapova]

+1

On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy <
asledzins...@mirantis.com> wrote:

> Hi,
> I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops [1]
> core.
>
> Alexey is doing great job improving fuel-qa and fuel-devops projects.
> He's become an expert in code base in very short terms so I think he
> deserves to be a part of fuel-qa/fuel-devops core team.
>
> Please, vote for Alexey!
>
> [0]
> http://stackalytics.com/?release=all=fuel-qa_id=astepanov-m=marks
> [1]
> http://stackalytics.com/?release=all=fuel-devops_id=astepanov-m=marks
>
> --
> Thanks,
> Andrey Sledzinskiy
> QA Engineer,
> Mirantis, Kharkiv
>
> __
> 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-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Andrey Sledzinskiy]

Hi,
I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops [1]
core.

Alexey is doing great job improving fuel-qa and fuel-devops projects.
He's become an expert in code base in very short terms so I think he
deserves to be a part of fuel-qa/fuel-devops core team.

Please, vote for Alexey!

[0]
http://stackalytics.com/?release=all=fuel-qa_id=astepanov-m=marks
[1]
http://stackalytics.com/?release=all=fuel-devops_id=astepanov-m=marks

-- 
Thanks,
Andrey Sledzinskiy
QA Engineer,
Mirantis, Kharkiv
__
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] [fuel] IRC meeting for Jul - 14

[Andrew Woodward]

The meeting agenda is again empty, so I'm calling the meeting canceled.

https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda

-- 

--

Andrew Woodward

Mirantis

Fuel Community Ambassador

Ceph Community
__
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] [Fuel] Mitaka stable branch

[Vladimir Kuklin]

Bogdan, Vladimir

*Regarding upgrades of Fuel Master Node and environments. *

First, regarding Fuel Master Node upgrades and enablement of usage of 9.0
LCM features with older clusters. It is assumed that we test usability of
Fuel Mitaka code with already deployed clusters, e.g. 8.0, 7.0 and so on.
Whenever an issue arise, we fix it. This would allow us to reuse newest
features to be able to enable LCM and newest orchestration and integration
capabilities with older clusters by essentially, calling old serializers
code within extensions pipeline, applying some pre- and postprocessing to
the serialized data. Here is an example of how it is done (Work in
progress):

https://review.openstack.org/#/c/333845/

This is an extension that first runs new LCM serializer which data is not
compatible with 9.0, but part of which we need for LCM engine (e.g.
'cluster context'), then we simply run 8.0 Serializer, add cluster info
into serialized data and then we just update 'upload_configuration' and
related tasks by simply copying them from Mitaka code of Fuel Library. I
proof-tested this by adding Sahara into already installed 8.0 cluster with
BVT scenario and it seems to be working.

*Regarding environments upgrades*

Having completed item #1 we should be able to run new orchestration against
old clusters, so that we can upgrade environments to newer versions,
esentially, by rolling reinstallation of control plane and resource nodes,
which means that as soon as new version of installed software (including
OpenStack, LMA toolchaing and other stuff) works fine with the feature-set
specified within the old cluster configuration, it should be OK to do so,
but this basically becomes a matter of building consistent upgrade path for
the particular environment.

*Conclusion*

Let's add bugfixing for management of old clusters and pre-9.0 clusters LCM
support into our RoadMap and we should be safe to go.

On Wed, Jul 13, 2016 at 12:23 PM, Bogdan Dobrelya 
wrote:

> On 07/13/2016 11:08 AM, Vladimir Kozhukalov wrote:
> >
> >
> > Few Q:
> > - Is the stable/mitaka the only stable branch in the scope of the
> > changes?
> >
> > ​Yes, this announce is only about Mitaka branch. All other stable
> > branches are to be treated as usual, i.e. no feature backports, bug
> > fixes only following "master first" policy, etc.
> >
> >
> > - As the master and stable/mitaka will diverge, the former might
> contain
> > backwards incompatible changes, ending up the upgrade paths from
> > stable/mitaka to future >=10.x releases will likely be *blocked* for
> its
> > life time. Any plans how to address that?
> >
> > - What about upgrade paths availability from the stable/* branches
> to:
> >   a) stable/mitaka
> >   b) future >=10.x releases?
> >
> > ​Fortunately, Fuel now has nice built-in LCM that allows to run
> > complicated custom scenarios (including reconfigurations/upgrades of
> > existent OpenStack clusters). Vladimir Kuklin is working hard on making
> > this LCM capabilities applicable to cases stable/* -> stable/mitaka. I
> > believe later we'll be able to implement stable/mitaka -> Newton, etc.
>
> That's OK for the upgrade process, while I'm not sure in the very
> upgrade *possibility* if we allowed backwards incompatible changes make
> it to the Newton. How would users upgrade from stable/mitaka to anything
> wich might be backwards incompatible and might break things? And
> features backported and being developed in both branches may conflict as
> well. All of this makes the upgrade barely possible, so any ideas how
> could we address that?
>
> >
> > Let's try to imagine we removed old role based serializers from Nailgun
> > in Newton release. The question is how are we going, for example, to
> > add/remove nodes to/from Kilo/Liberty clusters. The answer would be we
> > could add custom task graph and task based deployment engine to modify
> > old clusters. I'd like Vladimir Kuklin to give some additional details.
> >
> >
> >
> >
> > >
> >
>  __
> > > OpenStack Development Mailing List (not for usage questions)
> > > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > <
> http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
> >
> >
> > --
> > Best regards,
> > Bogdan Dobrelya,
> > Irc #bogdando
> >
> >
>  __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > <
> http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> >
> >
> 

Re: [openstack-dev] [Fuel] New version of fuel-devops (2.9.21)

[Dennis Dmitriev]

Hi Bogdan,

thanks for the question!

On 07/12/2016 10:26 AM, Bogdan Dobrelya wrote:
> On 07/12/2016 09:24 AM, Bogdan Dobrelya wrote:
>> Thank you for a hard work, that's a really great tool.
>>
>> Anyone who is interested, please note that fuel-devops, despite of the
>> name, may be used outside of Fuel and OpenStack as a really fast and
>> easy way to spin up VMs for a dev envs. Almost like a Vagrant, although
>> it gives you advanced templates [1] which is more flexible at least for
>> networking perhaps.
>>
>> By the way, fuel-devops folks, do you plan to add docs [2] for advanced
>> templating as well?
>>
Some docs with template examples are located in [1].
After merging a couple of important patches [2] [3] , we plan to improve
the auto documentation and get the complete manual for all the options,
then it can be placed to /fuel-docs/.

[1]
https://github.com/openstack/fuel-devops/tree/master/doc/source/template_examples
[2] https://review.openstack.org/#/c/333224/
[3] https://review.openstack.org/#/c/338496/

> Sorry, here is the correct docs link [3] :-)
>
>> [1]
>> https://specs.openstack.org/openstack/fuel-specs/specs/8.0/template-based-virtual-devops-environments.html
>> [2]
>> https://git.openstack.org/cgit/openstack/fuel-ccp-installer/tree/utils/jenkins/default30-kargo.yaml
> [3] http://docs.openstack.org/developer/fuel-docs/devdocs/devops.html
>
>>
>> On 07/11/2016 08:39 PM, Dennis Dmitriev wrote:
>>> Hi All,
>>>
>>> We are going to update the 'fuel-devops' framework on our product CI to
>>> the version 2.9.21.
>>>
>>> Changes since 2.9.20:
>>>
>>> * For devops:
>>>
>>>   - Scripts for export and import systest environments, based on
>>> external libvirt snapshots [1]
>>>   - Disable creation of nwfilters by default [2]
>>>   - Get rid from log.yaml file, logger and it's settings were moved into
>>> scripts [3]
>>>   - Do not use database ids in bridge and interface names, that allows
>>> to use several different virtual environments with different set of
>>> requirements on the same host [4] [5] [6]
>>>
>>> * For QA automation:
>>>
>>>   - 'ipaddr' was replaced with 'netaddr'  [7]
>>>   - Use keystoneauth1 package for authorization to Nailgun [8]
>>>   - Move the method execute_through_host() from fuel-qa to SSHClient [9]
>>>   - Methods that allow to change boot order and close tray for Node [10]
>>>   - Lots of SSHClient improvements [11] [12] [13] [14] [15]
>>>   - Improvements for compatibility with python3
>>>
>>> List of all changes can be found on github [16].
>>>
>>> [1] https://review.openstack.org/#/c/280573/
>>> [2] https://review.openstack.org/#/c/313082/
>>> [3] https://review.openstack.org/#/c/320366/
>>> [4] https://review.openstack.org/#/c/327082/
>>> [5] https://review.openstack.org/#/c/336057/
>>> [6] https://review.openstack.org/#/c/339811/
>>> [7] https://review.openstack.org/#/c/299428/
>>> [8] https://review.openstack.org/#/c/314505/
>>> [9] https://review.openstack.org/#/c/319920/
>>> [10] https://review.openstack.org/#/c/331660/
>>> [11] https://review.openstack.org/#/c/331120/
>>> [12] https://review.openstack.org/#/c/327656/
>>> [13] https://review.openstack.org/#/c/327180/
>>> [14] https://review.openstack.org/#/c/326462/
>>> [15] https://review.openstack.org/#/c/338161/
>>> [16] - https://github.com/openstack/fuel-devops/compare/2.9.20...release/2.9
>>>
>>
>

-- 
Regards,
Dennis Dmitriev
QA Engineer,
Mirantis Inc. http://www.mirantis.com
e-mail/jabber: dis.x...@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-dev] [Fuel][QA] Changes in requirements.txt in the fuel-qa repository

[Dennis Dmitriev]

Hi all,

Recently there was a change in the fuel-qa requirements [1], that can be
found in patches for 6.1, 7.0, 8.0, mitaka and master [2] [3] [4] [5] [6].

The goal is to split the requirements for system tests from requirements
for fuel-devops, which is mostly the part of the system configuration
than the separated package at the moment.
This allows to update packages for fuel-qa on every run of system tests
automatically, without manual tracking changes in [1].

* To setup a virtual environment, please use [7] instead of [1].  In the
[7] is the link to the fuel-devops source with necessary tag.

* To update requirements for fuel-qa system tests, there are two ways:

   - Install necessary packages from [1]  (it will be an additional 'pip
install' in your deploy script)
   - Run fuel-qa/utils/jenkin/system_tests.sh  with the key -N or export
the variable UPDATE_REQUIREMENTS='yes' . In this case, the script
system_tests.sh will try to install packages from [1] every run (pip
install [1] , without --upgrade), that will keep the requirements for
fuel-qa tests up-to-date automatically.   Also, there is a requirement
for fuel-devops as a package [8], which is also used by
system_tests.sh.  Fuel-devops is not packaged yet, so [8] cannot be used
for install the package, only for control that the necessary version of
the package is installed.

*Please* check your CI scripts that create virtual environments for
fuel-qa tests and update the requirements installation commands as soon
as possible!

[1]
https://raw.githubusercontent.com/openstack/fuel-qa/master/fuelweb_test/requirements.txt

[2] https://review.openstack.org/#/c/334552/
[3] https://review.openstack.org/#/c/340319/
[4] https://review.openstack.org/#/c/340332/
[5] https://review.openstack.org/#/c/340323/
[6] https://review.openstack.org/#/c/340325/
[7]
https://raw.githubusercontent.com/openstack/fuel-qa/master/fuelweb_test/requirements-devops-source.txt
[8]
https://raw.githubusercontent.com/openstack/fuel-qa/master/fuelweb_test/requirements-devops.txt


-- 
Regards,
Dennis Dmitriev
QA Engineer,
Mirantis Inc. http://www.mirantis.com
e-mail/jabber: dis.x...@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

Re: [openstack-dev] [Fuel] Mitaka stable branch

[Bogdan Dobrelya]

On 07/13/2016 11:08 AM, Vladimir Kozhukalov wrote:
> 
> 
> Few Q:
> - Is the stable/mitaka the only stable branch in the scope of the
> changes?
> 
> ​Yes, this announce is only about Mitaka branch. All other stable
> branches are to be treated as usual, i.e. no feature backports, bug
> fixes only following "master first" policy, etc.
> 
> 
> - As the master and stable/mitaka will diverge, the former might contain
> backwards incompatible changes, ending up the upgrade paths from
> stable/mitaka to future >=10.x releases will likely be *blocked* for its
> life time. Any plans how to address that?
> 
> - What about upgrade paths availability from the stable/* branches to:
>   a) stable/mitaka
>   b) future >=10.x releases?
> 
> ​Fortunately, Fuel now has nice built-in LCM that allows to run
> complicated custom scenarios (including reconfigurations/upgrades of
> existent OpenStack clusters). Vladimir Kuklin is working hard on making
> this LCM capabilities applicable to cases stable/* -> stable/mitaka. I
> believe later we'll be able to implement stable/mitaka -> Newton, etc.

That's OK for the upgrade process, while I'm not sure in the very
upgrade *possibility* if we allowed backwards incompatible changes make
it to the Newton. How would users upgrade from stable/mitaka to anything
wich might be backwards incompatible and might break things? And
features backported and being developed in both branches may conflict as
well. All of this makes the upgrade barely possible, so any ideas how
could we address that?

> 
> Let's try to imagine we removed old role based serializers from Nailgun
> in Newton release. The question is how are we going, for example, to
> add/remove nodes to/from Kilo/Liberty clusters. The answer would be we
> could add custom task graph and task based deployment engine to modify
> old clusters. I'd like Vladimir Kuklin to give some additional details.
> 
>  
> 
> 
> >
> __
> > 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
> >
> 
> 
> --
> Best regards,
> Bogdan Dobrelya,
> Irc #bogdando
> 
> __
> 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
> 


-- 
Best regards,
Bogdan Dobrelya,
Irc #bogdando

__
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] [Fuel] Mitaka stable branch

[Vladimir Kozhukalov]

>
> Few Q:
> - Is the stable/mitaka the only stable branch in the scope of the changes?
>
​Yes, this announce is only about Mitaka branch. All other stable branches
are to be treated as usual, i.e. no feature backports, bug fixes only
following "master first" policy, etc.

>
> - As the master and stable/mitaka will diverge, the former might contain
> backwards incompatible changes, ending up the upgrade paths from
> stable/mitaka to future >=10.x releases will likely be *blocked* for its
> life time. Any plans how to address that?
>
> - What about upgrade paths availability from the stable/* branches to:
>   a) stable/mitaka
>   b) future >=10.x releases?
>
> ​Fortunately, Fuel now has nice built-in LCM that allows to run
complicated custom scenarios (including reconfigurations/upgrades of
existent OpenStack clusters). Vladimir Kuklin is working hard on making
this LCM capabilities applicable to cases stable/* -> stable/mitaka. I
believe later we'll be able to implement stable/mitaka -> Newton, etc.

Let's try to imagine we removed old role based serializers from Nailgun in
Newton release. The question is how are we going, for example, to
add/remove nodes to/from Kilo/Liberty clusters. The answer would be we
could add custom task graph and task based deployment engine to modify old
clusters. I'd like Vladimir Kuklin to give some additional details.



>
> >
> __
> > 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
> >
>
>
> --
> Best regards,
> Bogdan Dobrelya,
> Irc #bogdando
>
> __
> 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] [Fuel] Mitaka stable branch

[Bogdan Dobrelya]

On 07/13/2016 10:17 AM, Vladimir Kozhukalov wrote:
> Dear colleagues,
> 
> I'd like to announce some of our plans on how we are going to
> support/develop Fuel Mitaka stable branch. The plan is as follows:
> 
> 0) We have been working hard and have fixed a lot of bugs in Mitaka
> branch as for late. This week we are going to announce 9.0.1 release
> which is stable and production ready.
> 
> 1) We are planning to backport onto stable Mitaka branch some (NOT all)
> features that are more or less regression safe. All such features will
> be thoroughly tested so to avoid lack of stability. Given this we expect
> master and stable branches will soon diverge a lot and thus it will soon
> be impossible to just cherry-pick  majority of features and bug fixes
> from master to stable and instead they often are to be re-implemented.
> It will likely require to spend twice as much time as we usually spend
> for every change that is to be landed both in master and stable.
> 
> 2) We are planning to make stable Mitaka branch even more stable and
> continue to fix bugs (even medium and low). We are not planning to
> always follow Stable Branches policy [1] and backport onto stable Mitaka
> branch only those bugs that are already merged to master. Some bugs will
> be first merged to stable and then ported to master. It is just for
> conveniece and development velocity. Since master and stable will
> diverge significantly, it won't make much sense to follow "master first"
> policy. But still all bugs that make sense both for master and for
> stable must be fixed in both these branches.
> 
> 3) Since Mitaka branch is expected to stay stable all the time, we are
> planning to set release tags (9.x) on stable branch approximately every
> month or so. We won't be forced to spend months on code freezing and
> stabilizing and thus we will be able to release features frequently (not
> all features but those are to be backported onto stable branch).

Few Q:
- Is the stable/mitaka the only stable branch in the scope of the changes?

- As the master and stable/mitaka will diverge, the former might contain
backwards incompatible changes, ending up the upgrade paths from
stable/mitaka to future >=10.x releases will likely be *blocked* for its
life time. Any plans how to address that?

- What about upgrade paths availability from the stable/* branches to:
  a) stable/mitaka
  b) future >=10.x releases?

> 
> 
> [1] http://docs.openstack.org/project-team-guide/stable-branches.html
> 
> 
> Vladimir Kozhukalov
> 
> 
> __
> 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
> 


-- 
Best regards,
Bogdan Dobrelya,
Irc #bogdando

__
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] [Fuel] Mitaka stable branch

[Vladimir Kozhukalov]

Dear colleagues,

I'd like to announce some of our plans on how we are going to
support/develop Fuel Mitaka stable branch. The plan is as follows:

0) We have been working hard and have fixed a lot of bugs in Mitaka branch
as for late. This week we are going to announce 9.0.1 release which is
stable and production ready.

1) We are planning to backport onto stable Mitaka branch some (NOT all)
features that are more or less regression safe. All such features will be
thoroughly tested so to avoid lack of stability. Given this we expect
master and stable branches will soon diverge a lot and thus it will soon be
impossible to just cherry-pick  majority of features and bug fixes from
master to stable and instead they often are to be re-implemented. It will
likely require to spend twice as much time as we usually spend for every
change that is to be landed both in master and stable.

2) We are planning to make stable Mitaka branch even more stable and
continue to fix bugs (even medium and low). We are not planning to always
follow Stable Branches policy [1] and backport onto stable Mitaka branch
only those bugs that are already merged to master. Some bugs will be first
merged to stable and then ported to master. It is just for conveniece and
development velocity. Since master and stable will diverge significantly,
it won't make much sense to follow "master first" policy. But still all
bugs that make sense both for master and for stable must be fixed in both
these branches.

3) Since Mitaka branch is expected to stay stable all the time, we are
planning to set release tags (9.x) on stable branch approximately every
month or so. We won't be forced to spend months on code freezing and
stabilizing and thus we will be able to release features frequently (not
all features but those are to be backported onto stable branch).


[1] http://docs.openstack.org/project-team-guide/stable-branches.html


Vladimir Kozhukalov
__
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] [Fuel] New version of fuel-devops (2.9.21)

[Bogdan Dobrelya]

On 07/12/2016 09:24 AM, Bogdan Dobrelya wrote:
> Thank you for a hard work, that's a really great tool.
> 
> Anyone who is interested, please note that fuel-devops, despite of the
> name, may be used outside of Fuel and OpenStack as a really fast and
> easy way to spin up VMs for a dev envs. Almost like a Vagrant, although
> it gives you advanced templates [1] which is more flexible at least for
> networking perhaps.
> 
> By the way, fuel-devops folks, do you plan to add docs [2] for advanced
> templating as well?
> 

Sorry, here is the correct docs link [3] :-)

> [1]
> https://specs.openstack.org/openstack/fuel-specs/specs/8.0/template-based-virtual-devops-environments.html
> [2]
> https://git.openstack.org/cgit/openstack/fuel-ccp-installer/tree/utils/jenkins/default30-kargo.yaml

[3] http://docs.openstack.org/developer/fuel-docs/devdocs/devops.html

> 
> 
> On 07/11/2016 08:39 PM, Dennis Dmitriev wrote:
>> Hi All,
>>
>> We are going to update the 'fuel-devops' framework on our product CI to
>> the version 2.9.21.
>>
>> Changes since 2.9.20:
>>
>> * For devops:
>>
>>   - Scripts for export and import systest environments, based on
>> external libvirt snapshots [1]
>>   - Disable creation of nwfilters by default [2]
>>   - Get rid from log.yaml file, logger and it's settings were moved into
>> scripts [3]
>>   - Do not use database ids in bridge and interface names, that allows
>> to use several different virtual environments with different set of
>> requirements on the same host [4] [5] [6]
>>
>> * For QA automation:
>>
>>   - 'ipaddr' was replaced with 'netaddr'  [7]
>>   - Use keystoneauth1 package for authorization to Nailgun [8]
>>   - Move the method execute_through_host() from fuel-qa to SSHClient [9]
>>   - Methods that allow to change boot order and close tray for Node [10]
>>   - Lots of SSHClient improvements [11] [12] [13] [14] [15]
>>   - Improvements for compatibility with python3
>>
>> List of all changes can be found on github [16].
>>
>> [1] https://review.openstack.org/#/c/280573/
>> [2] https://review.openstack.org/#/c/313082/
>> [3] https://review.openstack.org/#/c/320366/
>> [4] https://review.openstack.org/#/c/327082/
>> [5] https://review.openstack.org/#/c/336057/
>> [6] https://review.openstack.org/#/c/339811/
>> [7] https://review.openstack.org/#/c/299428/
>> [8] https://review.openstack.org/#/c/314505/
>> [9] https://review.openstack.org/#/c/319920/
>> [10] https://review.openstack.org/#/c/331660/
>> [11] https://review.openstack.org/#/c/331120/
>> [12] https://review.openstack.org/#/c/327656/
>> [13] https://review.openstack.org/#/c/327180/
>> [14] https://review.openstack.org/#/c/326462/
>> [15] https://review.openstack.org/#/c/338161/
>> [16] - https://github.com/openstack/fuel-devops/compare/2.9.20...release/2.9
>>
> 
> 


-- 
Best regards,
Bogdan Dobrelya,
Irc #bogdando

__
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] [Fuel] New version of fuel-devops (2.9.21)

[Bogdan Dobrelya]

Thank you for a hard work, that's a really great tool.

Anyone who is interested, please note that fuel-devops, despite of the
name, may be used outside of Fuel and OpenStack as a really fast and
easy way to spin up VMs for a dev envs. Almost like a Vagrant, although
it gives you advanced templates [1] which is more flexible at least for
networking perhaps.

By the way, fuel-devops folks, do you plan to add docs [2] for advanced
templating as well?

[1]
https://specs.openstack.org/openstack/fuel-specs/specs/8.0/template-based-virtual-devops-environments.html
[2]
https://git.openstack.org/cgit/openstack/fuel-ccp-installer/tree/utils/jenkins/default30-kargo.yaml


On 07/11/2016 08:39 PM, Dennis Dmitriev wrote:
> Hi All,
> 
> We are going to update the 'fuel-devops' framework on our product CI to
> the version 2.9.21.
> 
> Changes since 2.9.20:
> 
> * For devops:
> 
>   - Scripts for export and import systest environments, based on
> external libvirt snapshots [1]
>   - Disable creation of nwfilters by default [2]
>   - Get rid from log.yaml file, logger and it's settings were moved into
> scripts [3]
>   - Do not use database ids in bridge and interface names, that allows
> to use several different virtual environments with different set of
> requirements on the same host [4] [5] [6]
> 
> * For QA automation:
> 
>   - 'ipaddr' was replaced with 'netaddr'  [7]
>   - Use keystoneauth1 package for authorization to Nailgun [8]
>   - Move the method execute_through_host() from fuel-qa to SSHClient [9]
>   - Methods that allow to change boot order and close tray for Node [10]
>   - Lots of SSHClient improvements [11] [12] [13] [14] [15]
>   - Improvements for compatibility with python3
> 
> List of all changes can be found on github [16].
> 
> [1] https://review.openstack.org/#/c/280573/
> [2] https://review.openstack.org/#/c/313082/
> [3] https://review.openstack.org/#/c/320366/
> [4] https://review.openstack.org/#/c/327082/
> [5] https://review.openstack.org/#/c/336057/
> [6] https://review.openstack.org/#/c/339811/
> [7] https://review.openstack.org/#/c/299428/
> [8] https://review.openstack.org/#/c/314505/
> [9] https://review.openstack.org/#/c/319920/
> [10] https://review.openstack.org/#/c/331660/
> [11] https://review.openstack.org/#/c/331120/
> [12] https://review.openstack.org/#/c/327656/
> [13] https://review.openstack.org/#/c/327180/
> [14] https://review.openstack.org/#/c/326462/
> [15] https://review.openstack.org/#/c/338161/
> [16] - https://github.com/openstack/fuel-devops/compare/2.9.20...release/2.9
> 


-- 
Best regards,
Bogdan Dobrelya,
Irc #bogdando

__
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] [Fuel] New version of fuel-devops (2.9.21)

[Dennis Dmitriev]

Hi All,

We are going to update the 'fuel-devops' framework on our product CI to
the version 2.9.21.

Changes since 2.9.20:

* For devops:

  - Scripts for export and import systest environments, based on
external libvirt snapshots [1]
  - Disable creation of nwfilters by default [2]
  - Get rid from log.yaml file, logger and it's settings were moved into
scripts [3]
  - Do not use database ids in bridge and interface names, that allows
to use several different virtual environments with different set of
requirements on the same host [4] [5] [6]

* For QA automation:

  - 'ipaddr' was replaced with 'netaddr'  [7]
  - Use keystoneauth1 package for authorization to Nailgun [8]
  - Move the method execute_through_host() from fuel-qa to SSHClient [9]
  - Methods that allow to change boot order and close tray for Node [10]
  - Lots of SSHClient improvements [11] [12] [13] [14] [15]
  - Improvements for compatibility with python3

List of all changes can be found on github [16].

[1] https://review.openstack.org/#/c/280573/
[2] https://review.openstack.org/#/c/313082/
[3] https://review.openstack.org/#/c/320366/
[4] https://review.openstack.org/#/c/327082/
[5] https://review.openstack.org/#/c/336057/
[6] https://review.openstack.org/#/c/339811/
[7] https://review.openstack.org/#/c/299428/
[8] https://review.openstack.org/#/c/314505/
[9] https://review.openstack.org/#/c/319920/
[10] https://review.openstack.org/#/c/331660/
[11] https://review.openstack.org/#/c/331120/
[12] https://review.openstack.org/#/c/327656/
[13] https://review.openstack.org/#/c/327180/
[14] https://review.openstack.org/#/c/326462/
[15] https://review.openstack.org/#/c/338161/
[16] - https://github.com/openstack/fuel-devops/compare/2.9.20...release/2.9

-- 
Regards,
Dennis Dmitriev
QA Engineer,
Mirantis Inc. http://www.mirantis.com
e-mail/jabber: ddmitr...@mirantis.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-dev] [Fuel][Plugins] Please update your Fuel plugin's entries in DriverLog

[Irina Povolotskaya]

Hi to everyone,

please make sure your Fuel Plugin information in DriverLog [1] is
up-to-date, specifically:
- compatible OpenStack releases
- CI/CD
- maintainers list and their contact information.

Detailed instructions on working with DriverLog are found here [2].

Thank you.


[1] http://stackalytics.com/report/driverlog?project_id=openstack/fuel
[2]
https://wiki.openstack.org/wiki/DriverLog#How_To:_Add_a_new_Fuel_Plugin_to_DriverLog


-- 
Best regards,

Irina Povolotskaya
__
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] [Fuel] It is impossible to queue UpdateDnsmasqTask

[Aleksandr Didenko]

Hi,

well, we have only one DHCP server that serves multiple clusters. Actions
with those multiple clusters may affect DHCP server configuration. So
queueing tasks that change DHCP server configuration seems like a
reasonable way to fix the problem. So options 2 and 3 are much better than
1 or 4.

Regards,
Alex

On Thu, Jul 7, 2016 at 10:59 AM, Georgy Kibardin 
wrote:

> Continuing speaking to myself :)
>
> Option 4 implies that we generate puppet manifest with a set of admin
> networks instead of writing it into hiera. So, we get a two step task
> which, first, generates manifest with unique name and, second, calls puppet
> to apply it.
> However, theres still a problem with this approach. When we almost
> simultaneously delete environments A and B (and A goes a bit earlier)
> astute acknowledges two UpdateDnsmasqTask tasks for execution, however, it
> cannot guarantee that puppet for UpdateDnsmasqTask for env A will be
> executed earlier than for env B. This would lead to incorrect list of admin
> networks by the end of environment deletion.
>
> So the option 4 just doesn't work.
>
> On Wed, Jul 6, 2016 at 11:41 AM, Georgy Kibardin 
> wrote:
>
>> Bulat is suggesting to move with 4. He suggest to merge all actions of
>> UpdateDnsmasqTask into one puppet task. There are three actions: syncing
>> admin network list to heira, dhcp ranges update and cobbler sync. The
>> problem I see with this approach is that current implementation does not
>> suppose passing any additional data to "puppet apply". Cobbler sync seems
>> to be a reasonable part of updating dhcp ranges config.
>>
>> Best,
>> Georgy
>>
>> On Thu, Jun 16, 2016 at 7:25 PM, Georgy Kibardin 
>> wrote:
>>
>>> Hi All,
>>>
>>> Currently we can only run one instance of subj. at time. An attempt to
>>> run second one causes an exception. This behaviour at least may cause a
>>> cluster to stuck forever in "removing" state (reproduces here
>>> https://bugs.launchpad.net/fuel/+bug/1544493) or just produce
>>> incomprehensible "task already running" message. So we need to address the
>>> problem somehow. I see the following ways to fix it:
>>>
>>> 1. Just put the cluster into "error" state which would allow user to
>>> remove it later.
>>>   pros: simple and fixes the problem at hand (#1544493)
>>>   cons: it would be hard to detect "come againg later" situation; quite
>>> a lame behavior: why don't you "come again later" yourself.
>>>
>>> 2. Implement generic queueing in nailgun.
>>> pros: quite simple
>>> cons: it doesn't look like nailgun responsibility
>>>
>>> 3. Implement generic queueing in astute.
>>>pros: this behaviour makes sense for astute.
>>>cons: the implementation would be quite complex, we need to
>>> synchronize execution between separate worker processes.
>>>
>>> 4. Split the task so that each part would work with particular cluster.
>>>pros: we don't extend our execution model
>>>cons: untrivial implementation; no guarantee that we are always able
>>> to split master node tasks on per cluster basis.
>>>
>>> Best,
>>> Georgy
>>>
>>
>>
>
> __
> 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-dev] [Fuel] Support of deployment history in fake Nailgun

[Julia Aranovich]

Hello everyone,

We [Fuel UI team] are working now on UI implementation of deployment
history [1] and deployment graphs [2] features.

For our development process and covering the features by functional tests,
it is critical to extend fake Nailgun with emulation of a real deployment
execution [3].

Now fake Nailgun provides a history with all the tasks in pending status
for a finished deployment. And we expect to get ready/error tasks as well
with task start and end timestamps.
Emulation of a history of running deployment is also needed.

So, is it possible to support the features in fake Nailgun?

Best regards,
Julia

[1] https://blueprints.launchpad.net/fuel/+spec/ui-deployment-history
[2] https://blueprints.launchpad.net/fuel/+spec/ui-custom-graph
[3] https://bugs.launchpad.net/fuel/+bug/1593757
__
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] [fuel] Weekly meeting for July 7

[Andrew Woodward]

There is no agenda on the meeting again this week so I am calling it
canceled.

Thanks
-- 

--

Andrew Woodward

Mirantis

Fuel Community Ambassador

Ceph Community
__
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] [Fuel] Failed to install fuel master

[Stanislaw Bogatkin]

I believe it is a problem root. We put kickstart file as a kernel parameter
and custom usb creators sometimes do not take it to consideration. Use
plain diskdump for copy ISO onto usb stick and all should work properly in
this case. You can find more details in official documentation for Fuel 8.0
[0].

[0]
https://docs.mirantis.com/openstack/fuel/fuel-8.0/fuel-install-guide.html#install-prepare-install-media

On Thu, Jul 7, 2016 at 12:53 PM, Alioune  wrote:

> Hi guys,
> I'm using Fuel-8.0  iso, I used "Lili USB Creator" to write ISO to the
> USB.
> (I tried this process for ubuntu-server.iso and it worked correctly).
>
> Regards,
>
> On 7 July 2016 at 09:54, Stanislaw Bogatkin 
> wrote:
>
>> Hi guys,
>>
>> could you tell which way you used to write ISO to the USB stick?
>>
>> On Thu, Jul 7, 2016 at 9:17 AM, Jack Morgan 
>> wrote:
>>
>>> I'm pretty sure this is a USB stick install as I've seen the same
>>> failure on Fuel-8.0. Basically, the installer is not able to find the
>>> mounted drive to run the kickstart file. Duel layer DVD media or a virtual
>>> Fuel master are the only ways I've gotten Fuel-8.0 to install.
>>>
>>> On 07/05/2016 05:22 AM, Vladimir Kuklin wrote:
>>>
>>> Hi, Alioune
>>>
>>> Let's start with the most basic steps. Which Fuel are you using?
>>> And how do you install the node? Do you use USB stick or DVD or some
>>> IPMI virtual media? From what I see here it pretty much looks like, that
>>> this media is not inserted into the host.
>>>
>>> On Tue, Jul 5, 2016 at 3:11 PM, Alioune  wrote:
>>>
 Hi all,

 I'm trying to install fuel master using [1] on phycal server but the
 installation process fails and switches to a dracut console with the
 following error:

 dracut-initqueue[595] floppy0: no floppy controllers found
 dracut-initqueue[595] Warning: failed to fetck kickstart from
 hd:sr0:/ks.cfg
 dracut-initqueue[595] mount: no medium found on /dev/sr0
 dracut-initqueue[595] Warning: Cloud not boot
 dracut-initqueue[595] Warning: /dev/root does not exist


 Starting Dracut Emergency Shell
 Warning: /dev/root does not exist
 Generating "/run/initramfs/rdsosreport.txt"
 dracut:/#

 Any suggestion for solving that error ?

 Regards,

 [1]
 http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/install/install_prepare_install_media.html


 __
 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


>>>
>>>
>>> --
>>> Yours Faithfully,
>>> Vladimir Kuklin,
>>> Fuel Library Tech Lead,
>>> Mirantis, Inc.
>>> +7 (495) 640-49-04
>>> +7 (926) 702-39-68
>>> Skype kuklinvv
>>> 35bk3, Vorontsovskaya Str.
>>> Moscow, Russia,
>>> www.mirantis.com 
>>> www.mirantis.ru
>>> vkuk...@mirantis.com
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: 
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>> --
>>> Jack Morgan
>>> OPNFV Pharos Intel Lab
>>>
>>>
>>>
>>> __
>>> 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
>>>
>>>
>>
>>
>> --
>> with best regards,
>> Stan.
>>
>> __
>> 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
>
>


-- 
with best regards,
Stan.
__
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] [Fuel] Failed to install fuel master

[Alioune]

Hi guys,
I'm using Fuel-8.0  iso, I used "Lili USB Creator" to write ISO to the USB.
(I tried this process for ubuntu-server.iso and it worked correctly).

Regards,

On 7 July 2016 at 09:54, Stanislaw Bogatkin  wrote:

> Hi guys,
>
> could you tell which way you used to write ISO to the USB stick?
>
> On Thu, Jul 7, 2016 at 9:17 AM, Jack Morgan  wrote:
>
>> I'm pretty sure this is a USB stick install as I've seen the same failure
>> on Fuel-8.0. Basically, the installer is not able to find the mounted drive
>> to run the kickstart file. Duel layer DVD media or a virtual Fuel master
>> are the only ways I've gotten Fuel-8.0 to install.
>>
>> On 07/05/2016 05:22 AM, Vladimir Kuklin wrote:
>>
>> Hi, Alioune
>>
>> Let's start with the most basic steps. Which Fuel are you using?
>> And how do you install the node? Do you use USB stick or DVD or some IPMI
>> virtual media? From what I see here it pretty much looks like, that this
>> media is not inserted into the host.
>>
>> On Tue, Jul 5, 2016 at 3:11 PM, Alioune  wrote:
>>
>>> Hi all,
>>>
>>> I'm trying to install fuel master using [1] on phycal server but the
>>> installation process fails and switches to a dracut console with the
>>> following error:
>>>
>>> dracut-initqueue[595] floppy0: no floppy controllers found
>>> dracut-initqueue[595] Warning: failed to fetck kickstart from
>>> hd:sr0:/ks.cfg
>>> dracut-initqueue[595] mount: no medium found on /dev/sr0
>>> dracut-initqueue[595] Warning: Cloud not boot
>>> dracut-initqueue[595] Warning: /dev/root does not exist
>>>
>>>
>>> Starting Dracut Emergency Shell
>>> Warning: /dev/root does not exist
>>> Generating "/run/initramfs/rdsosreport.txt"
>>> dracut:/#
>>>
>>> Any suggestion for solving that error ?
>>>
>>> Regards,
>>>
>>> [1]
>>> http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/install/install_prepare_install_media.html
>>>
>>>
>>> __
>>> 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
>>>
>>>
>>
>>
>> --
>> Yours Faithfully,
>> Vladimir Kuklin,
>> Fuel Library Tech Lead,
>> Mirantis, Inc.
>> +7 (495) 640-49-04
>> +7 (926) 702-39-68
>> Skype kuklinvv
>> 35bk3, Vorontsovskaya Str.
>> Moscow, Russia,
>> www.mirantis.com 
>> www.mirantis.ru
>> vkuk...@mirantis.com
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> --
>> Jack Morgan
>> OPNFV Pharos Intel Lab
>>
>>
>> __
>> 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
>>
>>
>
>
> --
> with best regards,
> Stan.
>
> __
> 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] [Fuel] It is impossible to queue UpdateDnsmasqTask

[Georgy Kibardin]

Continuing speaking to myself :)

Option 4 implies that we generate puppet manifest with a set of admin
networks instead of writing it into hiera. So, we get a two step task
which, first, generates manifest with unique name and, second, calls puppet
to apply it.
However, theres still a problem with this approach. When we almost
simultaneously delete environments A and B (and A goes a bit earlier)
astute acknowledges two UpdateDnsmasqTask tasks for execution, however, it
cannot guarantee that puppet for UpdateDnsmasqTask for env A will be
executed earlier than for env B. This would lead to incorrect list of admin
networks by the end of environment deletion.

So the option 4 just doesn't work.

On Wed, Jul 6, 2016 at 11:41 AM, Georgy Kibardin 
wrote:

> Bulat is suggesting to move with 4. He suggest to merge all actions of
> UpdateDnsmasqTask into one puppet task. There are three actions: syncing
> admin network list to heira, dhcp ranges update and cobbler sync. The
> problem I see with this approach is that current implementation does not
> suppose passing any additional data to "puppet apply". Cobbler sync seems
> to be a reasonable part of updating dhcp ranges config.
>
> Best,
> Georgy
>
> On Thu, Jun 16, 2016 at 7:25 PM, Georgy Kibardin 
> wrote:
>
>> Hi All,
>>
>> Currently we can only run one instance of subj. at time. An attempt to
>> run second one causes an exception. This behaviour at least may cause a
>> cluster to stuck forever in "removing" state (reproduces here
>> https://bugs.launchpad.net/fuel/+bug/1544493) or just produce
>> incomprehensible "task already running" message. So we need to address the
>> problem somehow. I see the following ways to fix it:
>>
>> 1. Just put the cluster into "error" state which would allow user to
>> remove it later.
>>   pros: simple and fixes the problem at hand (#1544493)
>>   cons: it would be hard to detect "come againg later" situation; quite a
>> lame behavior: why don't you "come again later" yourself.
>>
>> 2. Implement generic queueing in nailgun.
>> pros: quite simple
>> cons: it doesn't look like nailgun responsibility
>>
>> 3. Implement generic queueing in astute.
>>pros: this behaviour makes sense for astute.
>>cons: the implementation would be quite complex, we need to
>> synchronize execution between separate worker processes.
>>
>> 4. Split the task so that each part would work with particular cluster.
>>pros: we don't extend our execution model
>>cons: untrivial implementation; no guarantee that we are always able
>> to split master node tasks on per cluster basis.
>>
>> Best,
>> Georgy
>>
>
>
__
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] [Fuel] Failed to install fuel master

[Stanislaw Bogatkin]

Hi guys,

could you tell which way you used to write ISO to the USB stick?

On Thu, Jul 7, 2016 at 9:17 AM, Jack Morgan  wrote:

> I'm pretty sure this is a USB stick install as I've seen the same failure
> on Fuel-8.0. Basically, the installer is not able to find the mounted drive
> to run the kickstart file. Duel layer DVD media or a virtual Fuel master
> are the only ways I've gotten Fuel-8.0 to install.
>
> On 07/05/2016 05:22 AM, Vladimir Kuklin wrote:
>
> Hi, Alioune
>
> Let's start with the most basic steps. Which Fuel are you using?
> And how do you install the node? Do you use USB stick or DVD or some IPMI
> virtual media? From what I see here it pretty much looks like, that this
> media is not inserted into the host.
>
> On Tue, Jul 5, 2016 at 3:11 PM, Alioune  wrote:
>
>> Hi all,
>>
>> I'm trying to install fuel master using [1] on phycal server but the
>> installation process fails and switches to a dracut console with the
>> following error:
>>
>> dracut-initqueue[595] floppy0: no floppy controllers found
>> dracut-initqueue[595] Warning: failed to fetck kickstart from
>> hd:sr0:/ks.cfg
>> dracut-initqueue[595] mount: no medium found on /dev/sr0
>> dracut-initqueue[595] Warning: Cloud not boot
>> dracut-initqueue[595] Warning: /dev/root does not exist
>>
>>
>> Starting Dracut Emergency Shell
>> Warning: /dev/root does not exist
>> Generating "/run/initramfs/rdsosreport.txt"
>> dracut:/#
>>
>> Any suggestion for solving that error ?
>>
>> Regards,
>>
>> [1]
>> http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/install/install_prepare_install_media.html
>>
>> __
>> 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
>>
>>
>
>
> --
> Yours Faithfully,
> Vladimir Kuklin,
> Fuel Library Tech Lead,
> Mirantis, Inc.
> +7 (495) 640-49-04
> +7 (926) 702-39-68
> Skype kuklinvv
> 35bk3, Vorontsovskaya Str.
> Moscow, Russia,
> www.mirantis.com 
> www.mirantis.ru
> vkuk...@mirantis.com
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> --
> Jack Morgan
> OPNFV Pharos Intel Lab
>
>
> __
> 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
>
>


-- 
with best regards,
Stan.
__
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] [Fuel] Failed to install fuel master

[Jack Morgan]

I'm pretty sure this is a USB stick install as I've seen the same
failure on Fuel-8.0. Basically, the installer is not able to find the
mounted drive to run the kickstart file. Duel layer DVD media or a
virtual Fuel master are the only ways I've gotten Fuel-8.0 to install.


On 07/05/2016 05:22 AM, Vladimir Kuklin wrote:
> Hi, Alioune
>
> Let's start with the most basic steps. Which Fuel are you using?
> And how do you install the node? Do you use USB stick or DVD or some
> IPMI virtual media? From what I see here it pretty much looks like,
> that this media is not inserted into the host.
>
> On Tue, Jul 5, 2016 at 3:11 PM, Alioune  > wrote:
>
> Hi all,
>
> I'm trying to install fuel master using [1] on phycal server but
> the installation process fails and switches to a dracut console
> with the following error:
>
> dracut-initqueue[595] floppy0: no floppy controllers found
> dracut-initqueue[595] Warning: failed to fetck kickstart from
> hd:sr0:/ks.cfg
> dracut-initqueue[595] mount: no medium found on /dev/sr0
> dracut-initqueue[595] Warning: Cloud not boot
> dracut-initqueue[595] Warning: /dev/root does not exist
>
>
> Starting Dracut Emergency Shell
> Warning: /dev/root does not exist
> Generating "/run/initramfs/rdsosreport.txt"
> dracut:/#
>
> Any suggestion for solving that error ?
>
> Regards,
>
> [1] 
> http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/install/install_prepare_install_media.html
>
> __
> 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
>
>
>
>
> -- 
> Yours Faithfully,
> Vladimir Kuklin,
> Fuel Library Tech Lead,
> Mirantis, Inc.
> +7 (495) 640-49-04
> +7 (926) 702-39-68
> Skype kuklinvv
> 35bk3, Vorontsovskaya Str.
> Moscow, Russia,
> www.mirantis.com 
> www.mirantis.ru 
> vkuk...@mirantis.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

-- 
Jack Morgan
OPNFV Pharos Intel Lab

__
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] [Fuel] It is impossible to queue UpdateDnsmasqTask

[Georgy Kibardin]

Bulat is suggesting to move with 4. He suggest to merge all actions of
UpdateDnsmasqTask into one puppet task. There are three actions: syncing
admin network list to heira, dhcp ranges update and cobbler sync. The
problem I see with this approach is that current implementation does not
suppose passing any additional data to "puppet apply". Cobbler sync seems
to be a reasonable part of updating dhcp ranges config.

Best,
Georgy

On Thu, Jun 16, 2016 at 7:25 PM, Georgy Kibardin 
wrote:

> Hi All,
>
> Currently we can only run one instance of subj. at time. An attempt to run
> second one causes an exception. This behaviour at least may cause a cluster
> to stuck forever in "removing" state (reproduces here
> https://bugs.launchpad.net/fuel/+bug/1544493) or just produce
> incomprehensible "task already running" message. So we need to address the
> problem somehow. I see the following ways to fix it:
>
> 1. Just put the cluster into "error" state which would allow user to
> remove it later.
>   pros: simple and fixes the problem at hand (#1544493)
>   cons: it would be hard to detect "come againg later" situation; quite a
> lame behavior: why don't you "come again later" yourself.
>
> 2. Implement generic queueing in nailgun.
> pros: quite simple
> cons: it doesn't look like nailgun responsibility
>
> 3. Implement generic queueing in astute.
>pros: this behaviour makes sense for astute.
>cons: the implementation would be quite complex, we need to synchronize
> execution between separate worker processes.
>
> 4. Split the task so that each part would work with particular cluster.
>pros: we don't extend our execution model
>cons: untrivial implementation; no guarantee that we are always able to
> split master node tasks on per cluster basis.
>
> Best,
> Georgy
>
__
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] [Fuel] Failed to install fuel master

[Vladimir Kuklin]

Hi, Alioune

Let's start with the most basic steps. Which Fuel are you using?
And how do you install the node? Do you use USB stick or DVD or some IPMI
virtual media? From what I see here it pretty much looks like, that this
media is not inserted into the host.

On Tue, Jul 5, 2016 at 3:11 PM, Alioune  wrote:

> Hi all,
>
> I'm trying to install fuel master using [1] on phycal server but the
> installation process fails and switches to a dracut console with the
> following error:
>
> dracut-initqueue[595] floppy0: no floppy controllers found
> dracut-initqueue[595] Warning: failed to fetck kickstart from
> hd:sr0:/ks.cfg
> dracut-initqueue[595] mount: no medium found on /dev/sr0
> dracut-initqueue[595] Warning: Cloud not boot
> dracut-initqueue[595] Warning: /dev/root does not exist
>
>
> Starting Dracut Emergency Shell
> Warning: /dev/root does not exist
> Generating "/run/initramfs/rdsosreport.txt"
> dracut:/#
>
> Any suggestion for solving that error ?
>
> Regards,
>
> [1]
> http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/install/install_prepare_install_media.html
>
> __
> 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
>
>


-- 
Yours Faithfully,
Vladimir Kuklin,
Fuel Library Tech Lead,
Mirantis, Inc.
+7 (495) 640-49-04
+7 (926) 702-39-68
Skype kuklinvv
35bk3, Vorontsovskaya Str.
Moscow, Russia,
www.mirantis.com 
www.mirantis.ru
vkuk...@mirantis.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-dev] [Fuel] Failed to install fuel master

[Alioune]

Hi all,

I'm trying to install fuel master using [1] on phycal server but the
installation process fails and switches to a dracut console with the
following error:

dracut-initqueue[595] floppy0: no floppy controllers found
dracut-initqueue[595] Warning: failed to fetck kickstart from hd:sr0:/ks.cfg
dracut-initqueue[595] mount: no medium found on /dev/sr0
dracut-initqueue[595] Warning: Cloud not boot
dracut-initqueue[595] Warning: /dev/root does not exist


Starting Dracut Emergency Shell
Warning: /dev/root does not exist
Generating "/run/initramfs/rdsosreport.txt"
dracut:/#

Any suggestion for solving that error ?

Regards,

[1]
http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/install/install_prepare_install_media.html
__
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] [Fuel] - Nominate Maksim Malchuk to Fuel Library Core

[Maksim Malchuk]

Hi All,

I'm very appreciate being a part of the Fuel project as core reviewers team!
Thank you all for nomination and for +1s!

On Mon, Jul 4, 2016 at 12:17 PM, Sergii Golovatiuk  wrote:

> Hi,
>
> Please welcome Maksim as he's just joined fuel-library Core Team!
>
> --
> Best regards,
> Sergii Golovatiuk,
> Skype #golserge
> IRC #holser
>
> On Tue, Jun 28, 2016 at 1:06 PM, Adam Heczko  wrote:
>
>> Although I'm not Fuel core, +1 from me to Maksim. Maksim is not only
>> excellent engineer but also very friendly and helpful folk.
>>
>> On Tue, Jun 28, 2016 at 12:19 PM, Georgy Kibardin > > wrote:
>>
>>> +1
>>>
>>> On Tue, Jun 28, 2016 at 1:12 PM, Kyrylo Galanov 
>>> wrote:
>>>
 +1

 On Tue, Jun 28, 2016 at 1:16 AM, Matthew Mosesohn <
 mmoses...@mirantis.com> wrote:

> +1. Maksim is an excellent reviewer.
>
> On Mon, Jun 27, 2016 at 6:06 PM, Alex Schultz 
> wrote:
> > +1
> >
> > On Mon, Jun 27, 2016 at 9:04 AM, Bogdan Dobrelya <
> bdobre...@mirantis.com>
> > wrote:
> >>
> >> On 06/27/2016 04:54 PM, Sergii Golovatiuk wrote:
> >> > I am very sorry for sending without subject. I am adding subject
> to
> >> > voting and my +1
> >>
> >> +1 from my side!
> >>
> >> >
> >> > --
> >> > Best regards,
> >> > Sergii Golovatiuk,
> >> > Skype #golserge
> >> > IRC #holser
> >> >
> >> > On Mon, Jun 27, 2016 at 4:42 PM, Sergii Golovatiuk
> >> > >
> wrote:
> >> >
> >> > Hi,
> >> >
> >> > I would like to nominate Maksim Malchuk to Fuel-Library Core
> team.
> >> > He’s been doing a great job so far [0]. He’s #2 reviewer and
> #2
> >> > contributor with 28 commits for last 90 days [1][2].
> >> >
> >> > Fuelers, please vote with +1/-1 for approval/objection.
> Voting will
> >> > be open until July of 4th. This will go forward after voting
> is
> >> > closed if there are no objections.
> >> >
> >> > Overall contribution:
> >> > [0] http://stackalytics.com/?user_id=mmalchuk
> >> > Fuel library contribution for last 90 days:
> >> > [1]
> >> > 
> http://stackalytics.com/report/contribution/fuel-library/90
> >> > http://stackalytics.com/report/users/mmalchuk
> >> > List of reviews:
> >> > [2]
> >> >
> https://review.openstack.org/#/q/reviewer:%22Maksim+Malchuk%22+status:merged,n,z
> >> > --
> >> > Best regards,
> >> > Sergii Golovatiuk,
> >> > Skype #golserge
> >> > IRC #holser
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> __
> >> > 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
> >> >
> >>
> >>
> >> --
> >> Best regards,
> >> Bogdan Dobrelya,
> >> Irc #bogdando
> >>
> >>
> __
> >> 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
>



 __
 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
>>> 

Re: [openstack-dev] [Fuel] - Nominate Maksim Malchuk to Fuel Library Core

[Sergii Golovatiuk]

Hi,

Please welcome Maksim as he's just joined fuel-library Core Team!

--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser

On Tue, Jun 28, 2016 at 1:06 PM, Adam Heczko  wrote:

> Although I'm not Fuel core, +1 from me to Maksim. Maksim is not only
> excellent engineer but also very friendly and helpful folk.
>
> On Tue, Jun 28, 2016 at 12:19 PM, Georgy Kibardin 
> wrote:
>
>> +1
>>
>> On Tue, Jun 28, 2016 at 1:12 PM, Kyrylo Galanov 
>> wrote:
>>
>>> +1
>>>
>>> On Tue, Jun 28, 2016 at 1:16 AM, Matthew Mosesohn <
>>> mmoses...@mirantis.com> wrote:
>>>
 +1. Maksim is an excellent reviewer.

 On Mon, Jun 27, 2016 at 6:06 PM, Alex Schultz 
 wrote:
 > +1
 >
 > On Mon, Jun 27, 2016 at 9:04 AM, Bogdan Dobrelya <
 bdobre...@mirantis.com>
 > wrote:
 >>
 >> On 06/27/2016 04:54 PM, Sergii Golovatiuk wrote:
 >> > I am very sorry for sending without subject. I am adding subject to
 >> > voting and my +1
 >>
 >> +1 from my side!
 >>
 >> >
 >> > --
 >> > Best regards,
 >> > Sergii Golovatiuk,
 >> > Skype #golserge
 >> > IRC #holser
 >> >
 >> > On Mon, Jun 27, 2016 at 4:42 PM, Sergii Golovatiuk
 >> > >
 wrote:
 >> >
 >> > Hi,
 >> >
 >> > I would like to nominate Maksim Malchuk to Fuel-Library Core
 team.
 >> > He’s been doing a great job so far [0]. He’s #2 reviewer and #2
 >> > contributor with 28 commits for last 90 days [1][2].
 >> >
 >> > Fuelers, please vote with +1/-1 for approval/objection. Voting
 will
 >> > be open until July of 4th. This will go forward after voting is
 >> > closed if there are no objections.
 >> >
 >> > Overall contribution:
 >> > [0] http://stackalytics.com/?user_id=mmalchuk
 >> > Fuel library contribution for last 90 days:
 >> > [1]
 >> > 
 http://stackalytics.com/report/contribution/fuel-library/90
 >> > http://stackalytics.com/report/users/mmalchuk
 >> > List of reviews:
 >> > [2]
 >> >
 https://review.openstack.org/#/q/reviewer:%22Maksim+Malchuk%22+status:merged,n,z
 >> > --
 >> > Best regards,
 >> > Sergii Golovatiuk,
 >> > Skype #golserge
 >> > IRC #holser
 >> >
 >> >
 >> >
 >> >
 >> >
 >> >
 __
 >> > 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
 >> >
 >>
 >>
 >> --
 >> Best regards,
 >> Bogdan Dobrelya,
 >> Irc #bogdando
 >>
 >>
 __
 >> 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

>>>
>>>
>>>
>>> __
>>> 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
>>
>>
>
>
> --
> Adam Heczko
> Security Engineer @ Mirantis Inc.
>
> __
> 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] [fuel][nailgun-agent] Announcement of massive changes in fuel-nailgun-agent

[Ivan Suzdal]

Greetings!

Today we did a big change which might be invasive. We replaced ohai with facter 
in fuel-nailgun-agent [1]. There were a couple reasons why we did that:

1. Fuel project uses facter very intensively. However, ohai and facter have 
similar purpose and functionality. We were lack of some useful features from 
ohai.
2. Ohai requires a lot of dependencies. Every dependency is a separate package 
which requires some efforts to maintain it.

All necessary functionality was added to nailgun-agent so we have a feature 
parity at the moment. Since the change is big it might be dangerous as it’s 
related to hardware where it’s run on. Please don’t hesitate to contact me in 
case of any issues with nailgun-agent. Your feedback is appreciated.

[1] https://review.openstack.org/#/c/314642/ 



Best regards!
Ivan Suzdal
isuz...@mirantis.com





signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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] [FUEL]Network verification failed.

[Aleksey Zvyagintsev]

Hi
I guess, this doc[1] will be more useful - since Samer use fuel 8.0

[1] https://community.mellanox.com/docs/DOC-2435

On Thu, Jun 30, 2016 at 6:18 PM, Yuki Nishiwaki 
wrote:

> Hello Samer
>
> Did you read this reference (https://community.mellanox.com/docs/DOC-2036)
> ?
> If you didn’t read it yet, this may be helpful to you.
>
> By the way, "Figure 1” which is attached is very cool chart.
> What the tool did you use to write this figure ??
>
> Yuki Nishiwaki
>
> 2016/06/30 21:01、Samer Machara  のメール：
>
> Hello!
>   I'm having problems configuring the Network settings (See Figure 3) in
> Fuel 8.0. In Figure 1, I resume my network topology.
>
>   When I am checking the network, I get the following error: verification
> failed Expected VLAN (not received). See Figure 2.
>
>   All these Node interfaces correspond to the "storage network" that are
> type "InfiniBand" connected to a switch "Mellanox IS5025"
> unmanaged, which means it is plug and play. So, I can not configure PKs
> (VLANs).
>
>
>   Otherwise, I do not know how to determine what is happening because I do
> not see more details of the error, other than that shown in Fig 2.
>
> 
> Figure 1
>
> 
> Figure 2.
>
>
> 
> Figure 3
>
> __
> 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
>
>


-- 
---
Best regards,
   Aleksey Zvyagintsev
__
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] [Fuel][QA] fuel-devops bridge and interface names

[Anton Studenov]

Hi to all,

This message is related to upcoming changes in fuel-devops project.

Race condition issue was found in scenario where multiple environments
are being created at the same time. Networks or node interfaces recive
the same name in different environmens and this leads to error.
This happens because in the current implementation of fuel-devops
the names are assigned manually in code. We'd like to change this
and make libvirt to choose available names because libvirt has such feature
and it would be easier to use it rather than look for available names.

After proposed changes[1][2], fuel-devops will use the following prefixes:
  virbr - for network bridge names
  vnet - for node interface names

Concerns/Proposals are welcome.


[1] https://review.openstack.org/#/c/336057/ for release/2.9 branch
[2] https://review.openstack.org/#/c/336064/ for master branch

Thanks,
Anton

__
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] [Fuel][Ci] New 'fuel-nailgun' gate job

[Dmitry Kaiharodsev]

Hi to all,

please be informed that we've enabled voting on mentioned Jenkins jobs

For any additional questions please use our #fuel-infra IRC channel

On Tue, Jun 7, 2016 at 3:59 PM, Dmitry Kaiharodsev <
dkaiharod...@mirantis.com> wrote:

> Hi to all,
>
> please be informed that starting from today we're launching gate job [1]
> for 'fuel-nailgun' package [2] in non-voting mode.
>
> Mentioned job will be triggered on each commit and will perform steps:
> - build a package from the commit
> - run system tests scenario [3] with using created package
> - show system test result in current patchset without voting
>
> We're going to enable voting mode when it will be approved from 'fuel-qa'
> team side.
> Additional notification regarding voting mode will be sent in this thread.
>
> For any additional questions please use our #fuel-infra IRC channel
>
> [1] https://bugs.launchpad.net/fuel/+bug/1557524
> [2] https://github.com/openstack/fuel-nailgun-agent
> [3]
> https://github.com/openstack/fuel-qa/blob/master/gates_tests/tests/test_nailgun_agent.py#L38-45
>
> --
> Kind Regards,
> Dmitry Kaigarodtsev
> IRC: dkaigarodtsev
>



-- 
Kind Regards,
Dmitry Kaigarodtsev
IRC: dkaigarodtsev
__
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] [FUEL]Network verification failed.

[Yuki Nishiwaki]

Hello Samer

Did you read this reference (https://community.mellanox.com/docs/DOC-2036) ?
If you didn’t read it yet, this may be helpful to you.

By the way, "Figure 1” which is attached is very cool chart.
What the tool did you use to write this figure ??

Yuki Nishiwaki

> 2016/06/30 21:01、Samer Machara  のメール：
> 
> Hello!
>   I'm having problems configuring the Network settings (See Figure 3) in Fuel 
> 8.0. In Figure 1, I resume my network topology.
>  
>   When I am checking the network, I get the following error: verification 
> failed Expected VLAN (not received). See Figure 2.
> 
>   All these Node interfaces correspond to the "storage network" that are type 
> "InfiniBand" connected to a switch "Mellanox IS5025"
> unmanaged, which means it is plug and play. So, I can not configure PKs 
> (VLANs).
>  
>   Otherwise, I do not know how to determine what is happening because I do 
> not see more details of the error, other than that shown in Fig 2.
> 
> 
> Figure 1
> 
> 
> Figure 2.
> 
> 
> 
> Figure 3
> 
> __
> 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-dev] [fuel] Weekly meeting 6/30 Cancled

[Andrew Woodward]

Nothing is on the agenda this week, so I'm calling to cancel the meeting.
If you have anything to discuss. Please come chat in #fuel or add it to the
agenda to discuss next week.

https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
-- 

--

Andrew Woodward

Mirantis

Fuel Community Ambassador

Ceph Community
__
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] [Fuel] Deprecation of fuel-mirror tool

[Vladimir Kozhukalov]

Please review this patch [1]. It is to remove the code from master branch.
We still need test jobs for stable branches.

[1] https://review.openstack.org/#/c/335868/

Vladimir Kozhukalov

On Mon, Jun 27, 2016 at 1:14 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:

> Fuel-mirror python module itself will be removed from fuel-mirror
> repository, but perestroika is to be there until Packetary is able to
> substitute perestroika totally (work is now in progress).
>
> Just a reminder: According to our plan Packetary is to cover the whole
> rpm/deb domain including building deb/rpm packages and repositories.
> Sincing these repos over multiple locations as well as tracking repository
> snapshots will be a matter of Trsync project (Fuel infra team project).
>
> Vladimir Kozhukalov
>
> On Mon, Jun 27, 2016 at 11:38 AM, Igor Kalnitsky 
> wrote:
>
>> Vladimir,
>>
>> Thanks for driving this! What about fuel-mirror itself? Does it mean it's
>> deprecated? If so, what will happen to perestroika scripts inside it [1]?
>> It seems strange that fuel-mirror contains them.
>>
>> Thanks,
>> Igor
>>
>> [1] https://github.com/openstack/fuel-mirror/tree/master/perestroika
>>
>>
>> > On Jun 23, 2016, at 13:31, Vladimir Kozhukalov <
>> vkozhuka...@mirantis.com> wrote:
>> >
>> > Dear colleagues.
>> >
>> > I'd like to announce that fuel-mirror tool is not going to be a part of
>> Fuel any more. Its functionality is to build/clone rpm/deb repos and modify
>> Fuel releases repository lists (metadata).
>> >
>> > Since Fuel 10.0 it is recommended to use other available tools for
>> managing local deb/rpm repositories.
>> >
>> > Packetary is a good example [0]. Packetary is ideal if one needs to
>> create a partial mirror of a deb/rpm repository, i.e. mirror that contains
>> not all available packages but only a subset of packages. To create full
>> mirror it is better to use debmirror or rsync or any other tools that are
>> available.
>> >
>> > To modify releases repository lists one can use commands which are to
>> available by default on the Fuel admin node since Newton.
>> >
>> > # list of available releases
>> > fuel2 release list
>> > # list of repositories for a release
>> > fuel2 release repos list 
>> > # save list of repositories for a release in yaml format
>> > fuel2 release repos list  -f yaml | tee repos.yaml
>> > # modify list of repositories
>> > vim repos.yaml
>> > # update list of repositories for a release from yaml file
>> > fuel2 release repos update  -f repos.yaml
>> >
>> > They are provided by python-fuelclient [1] package and were introduced
>> by this [2] patch.
>> >
>> >
>> > [0] https://wiki.openstack.org/wiki/Packetary
>> > [1] https://github.com/openstack/python-fuelclient
>> > [2] https://review.openstack.org/#/c/326435/
>> >
>> >
>> > Vladimir Kozhukalov
>> >
>> __
>> > 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

Re: [openstack-dev] [Fuel] Deprecate fuel-upgrade repository

[Vladimir Kozhukalov]

Yet another patch [1] that makes fuel-upgrade read only.

[1] https://review.openstack.org/#/c/335841/

Vladimir Kozhukalov

On Wed, Jun 29, 2016 at 6:42 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:

> This is yet another related patch [1], that removes the code from master
> branch and adds retirement warning. Review is welcome.
>
> [1] https://review.openstack.org/#/c/334949/
>
>
> Vladimir Kozhukalov
>
> On Wed, Jun 29, 2016 at 4:00 PM, Ilya Kharin  wrote:
>
>> Hi Vladimir,
>>
>> This change is reasonable because the fuel-upgrade repository is not
>> supported since the 8.0 release due to the fact that upgrade activities
>> were consolidated in the fuel-octane repository. Also, as I know upgrade
>> tarballs are no longer supported for the old releases (less or equal 7.0).
>>
>> I see only one concern here that it can prevent to create some fixes for
>> upgrade tarballs for old realease. Otherwise I have not any objections to
>> send this repository on the retirement.
>>
>> Best regards,
>> Ilya Kharin.
>>
>> On Tue, Jun 28, 2016 at 6:18 PM Vladimir Kozhukalov <
>> vkozhuka...@mirantis.com> wrote:
>>
>>> This patch [1] is a part of project retirement procedure [2]. Review is
>>> welcome.
>>>
>>> [1] https://review.openstack.org/#/c/335085/
>>> [2]
>>> http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
>>>
>>> Vladimir Kozhukalov
>>>
>>> On Tue, Jun 28, 2016 at 1:41 PM, Vladimir Kozhukalov <
>>> vkozhuka...@mirantis.com> wrote:
>>>
 Dear colleagues,

 Please be informed that fuel-upgrade [1] repository is going to be
 deprecated. We used to develop Fuel admin node upgrade scenarios in this
 repo, but now all upgrade related stuff is in fuel-octane [2] repo. So,
 fuel-upgrade is to be removed from the list of official Fuel repos [3].
 Fuel-upgrade will stay available for a while perhaps for about a year or so
 in case some of Fuel users want to build upgrade tarball.


 [1] https://github.com/openstack/fuel-upgrade
 [2] https://github.com/openstack/fuel-octane
 [3] https://review.openstack.org/#/c/334903/

 Vladimir Kozhukalov

>>>
>>>
>>> __
>>> 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

Re: [openstack-dev] [Fuel] Deprecate fuel-upgrade repository

[Vladimir Kozhukalov]

This is yet another related patch [1], that removes the code from master
branch and adds retirement warning. Review is welcome.

[1] https://review.openstack.org/#/c/334949/


Vladimir Kozhukalov

On Wed, Jun 29, 2016 at 4:00 PM, Ilya Kharin  wrote:

> Hi Vladimir,
>
> This change is reasonable because the fuel-upgrade repository is not
> supported since the 8.0 release due to the fact that upgrade activities
> were consolidated in the fuel-octane repository. Also, as I know upgrade
> tarballs are no longer supported for the old releases (less or equal 7.0).
>
> I see only one concern here that it can prevent to create some fixes for
> upgrade tarballs for old realease. Otherwise I have not any objections to
> send this repository on the retirement.
>
> Best regards,
> Ilya Kharin.
>
> On Tue, Jun 28, 2016 at 6:18 PM Vladimir Kozhukalov <
> vkozhuka...@mirantis.com> wrote:
>
>> This patch [1] is a part of project retirement procedure [2]. Review is
>> welcome.
>>
>> [1] https://review.openstack.org/#/c/335085/
>> [2]
>> http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
>>
>> Vladimir Kozhukalov
>>
>> On Tue, Jun 28, 2016 at 1:41 PM, Vladimir Kozhukalov <
>> vkozhuka...@mirantis.com> wrote:
>>
>>> Dear colleagues,
>>>
>>> Please be informed that fuel-upgrade [1] repository is going to be
>>> deprecated. We used to develop Fuel admin node upgrade scenarios in this
>>> repo, but now all upgrade related stuff is in fuel-octane [2] repo. So,
>>> fuel-upgrade is to be removed from the list of official Fuel repos [3].
>>> Fuel-upgrade will stay available for a while perhaps for about a year or so
>>> in case some of Fuel users want to build upgrade tarball.
>>>
>>>
>>> [1] https://github.com/openstack/fuel-upgrade
>>> [2] https://github.com/openstack/fuel-octane
>>> [3] https://review.openstack.org/#/c/334903/
>>>
>>> Vladimir Kozhukalov
>>>
>>
>> __
>> 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

Re: [openstack-dev] [Fuel] Deprecate fuel-upgrade repository

[Ilya Kharin]

Hi Vladimir,

This change is reasonable because the fuel-upgrade repository is not
supported since the 8.0 release due to the fact that upgrade activities
were consolidated in the fuel-octane repository. Also, as I know upgrade
tarballs are no longer supported for the old releases (less or equal 7.0).

I see only one concern here that it can prevent to create some fixes for
upgrade tarballs for old realease. Otherwise I have not any objections to
send this repository on the retirement.

Best regards,
Ilya Kharin.

On Tue, Jun 28, 2016 at 6:18 PM Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:

> This patch [1] is a part of project retirement procedure [2]. Review is
> welcome.
>
> [1] https://review.openstack.org/#/c/335085/
> [2] http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
>
> Vladimir Kozhukalov
>
> On Tue, Jun 28, 2016 at 1:41 PM, Vladimir Kozhukalov <
> vkozhuka...@mirantis.com> wrote:
>
>> Dear colleagues,
>>
>> Please be informed that fuel-upgrade [1] repository is going to be
>> deprecated. We used to develop Fuel admin node upgrade scenarios in this
>> repo, but now all upgrade related stuff is in fuel-octane [2] repo. So,
>> fuel-upgrade is to be removed from the list of official Fuel repos [3].
>> Fuel-upgrade will stay available for a while perhaps for about a year or so
>> in case some of Fuel users want to build upgrade tarball.
>>
>>
>> [1] https://github.com/openstack/fuel-upgrade
>> [2] https://github.com/openstack/fuel-octane
>> [3] https://review.openstack.org/#/c/334903/
>>
>> Vladimir Kozhukalov
>>
>
> __
> 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] [Fuel][Plugins] Fuel Plugin Builder 4.1.0 released!

[Jonnalagadda, Venkata]

Wow! Thanks Igor for the update.

Thanks & Regards,

J. Venkata Mahesh



-Original Message-
From: Igor Kalnitsky [mailto:ikalnit...@mirantis.com] 
Sent: Wednesday, June 29, 2016 5:58 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [Fuel][Plugins] Fuel Plugin Builder 4.1.0 released!

Hey Fuelers,

I'm glad to announce that FPB (fuel plugin builder) v4.1.0 has been released on 
PyPI [1].

It's mostly a maintenance release without new features. Here's a changelog 
highlights:

* `tasks.yaml` is now optional for package version "4.0.0" [2]
* Fuel Mitaka (9.0) is supported by default in package version "4.0.0" [3]
* Use more reliable way to check for `fpm` Ruby GEM [4]
* Add ability for role to conflict with all roles by using `*` sign [5]
* Do not execute `uninstall.sh` on plugin upgrade [6]
* Add possiblity to use generators in `environment_config.yaml` [7]
* Don't put any code to PREUN section if `uninstall.sh` doesn't exist or empty 
[8]
* Allow a user to specify any arbitrary string as role name for cross-deps [9]
* Add deployment tasks v2.1 validation support [10]

- Igor


[1]: https://pypi.io/project/fuel-plugin-builder/4.1.0/
[2]: https://bugs.launchpad.net/fuel/+bug/1552248
[3]: https://bugs.launchpad.net/fuel/+bug/1549276
[4]: https://bugs.launchpad.net/fuel/+bug/1561069
[5]: https://bugs.launchpad.net/fuel/+bug/1547590
[6]: https://bugs.launchpad.net/fuel/+bug/1564123
[7]: https://bugs.launchpad.net/fuel/+bug/1557562
[8]: https://bugs.launchpad.net/fuel/+bug/1574478
[9]: https://bugs.launchpad.net/fuel/+bug/1557997
[10]: https://bugs.launchpad.net/fuel/+bug/1590389

__
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] [Fuel][Plugins] Fuel Plugin Builder 4.1.0 released!

[Michal Skalski]

Hi,

Great news, thanks!

Regards,
Michal
> On 29 Jun 2016, at 14:28, Igor Kalnitsky  wrote:
> 
> Hey Fuelers,
> 
> I'm glad to announce that FPB (fuel plugin builder) v4.1.0 has been
> released on PyPI [1].
> 
> It's mostly a maintenance release without new features. Here's a
> changelog highlights:
> 
> * `tasks.yaml` is now optional for package version "4.0.0" [2]
> * Fuel Mitaka (9.0) is supported by default in package version "4.0.0" [3]
> * Use more reliable way to check for `fpm` Ruby GEM [4]
> * Add ability for role to conflict with all roles by using `*` sign [5]
> * Do not execute `uninstall.sh` on plugin upgrade [6]
> * Add possiblity to use generators in `environment_config.yaml` [7]
> * Don't put any code to PREUN section if `uninstall.sh` doesn't exist
> or empty [8]
> * Allow a user to specify any arbitrary string as role name for cross-deps [9]
> * Add deployment tasks v2.1 validation support [10]
> 
> - Igor
> 
> 
> [1]: https://pypi.io/project/fuel-plugin-builder/4.1.0/
> [2]: https://bugs.launchpad.net/fuel/+bug/1552248
> [3]: https://bugs.launchpad.net/fuel/+bug/1549276
> [4]: https://bugs.launchpad.net/fuel/+bug/1561069
> [5]: https://bugs.launchpad.net/fuel/+bug/1547590
> [6]: https://bugs.launchpad.net/fuel/+bug/1564123
> [7]: https://bugs.launchpad.net/fuel/+bug/1557562
> [8]: https://bugs.launchpad.net/fuel/+bug/1574478
> [9]: https://bugs.launchpad.net/fuel/+bug/1557997
> [10]: https://bugs.launchpad.net/fuel/+bug/1590389
> 
> __
> 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-dev] [Fuel][Plugins] Fuel Plugin Builder 4.1.0 released!

[Igor Kalnitsky]

Hey Fuelers,

I'm glad to announce that FPB (fuel plugin builder) v4.1.0 has been
released on PyPI [1].

It's mostly a maintenance release without new features. Here's a
changelog highlights:

* `tasks.yaml` is now optional for package version "4.0.0" [2]
* Fuel Mitaka (9.0) is supported by default in package version "4.0.0" [3]
* Use more reliable way to check for `fpm` Ruby GEM [4]
* Add ability for role to conflict with all roles by using `*` sign [5]
* Do not execute `uninstall.sh` on plugin upgrade [6]
* Add possiblity to use generators in `environment_config.yaml` [7]
* Don't put any code to PREUN section if `uninstall.sh` doesn't exist
or empty [8]
* Allow a user to specify any arbitrary string as role name for cross-deps [9]
* Add deployment tasks v2.1 validation support [10]

- Igor


[1]: https://pypi.io/project/fuel-plugin-builder/4.1.0/
[2]: https://bugs.launchpad.net/fuel/+bug/1552248
[3]: https://bugs.launchpad.net/fuel/+bug/1549276
[4]: https://bugs.launchpad.net/fuel/+bug/1561069
[5]: https://bugs.launchpad.net/fuel/+bug/1547590
[6]: https://bugs.launchpad.net/fuel/+bug/1564123
[7]: https://bugs.launchpad.net/fuel/+bug/1557562
[8]: https://bugs.launchpad.net/fuel/+bug/1574478
[9]: https://bugs.launchpad.net/fuel/+bug/1557997
[10]: https://bugs.launchpad.net/fuel/+bug/1590389

__
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] [Fuel][Plugins] Transition of SDK to docs.openstack.org

[Irina Povolotskaya]

Hi to everyone,

please be informed that Fuel Plugin SDK is being migrated to
docs.openstack.org to deliver a better dev. experience and versioning.

the current version placed here [1] features the very initial revision of
the SDK, with no specifics of the wiki page content  [2].

*REQUEST:*
if you have some extra feedback for SDK (e.g. for non-documented features),
you are very welcome to file a bug report following instructions [3].

thanks to everyone who contributed to SDK!

[1]
http://docs.openstack.org/developer/fuel-docs/plugindocs/fuel-plugin-sdk-guide.html
[2] https://wiki.openstack.org/wiki/Fuel/Plugins
[3]
http://docs.openstack.org/developer/fuel-docs/plugindocs/fuel-plugin-sdk-guide/additional-information.html

-- 
Best regards,

Irina Povolotskaya
__
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] [Fuel] Replace OSTF with Rally

[Alexander Kostrikov]

Boris, can You take a look on HA scenarios [0] to give a quick feedback on
how it should be implemented with Rally in right way? Plugins/templates/how
yaml should look like.
To make correct comparison of ostf and rally-based version.

Thanks!
[0] http://paste.openstack.org/show/523983/

On Tue, Jun 28, 2016 at 3:34 AM, Boris Pavlovic 
wrote:

> Igor,
>
>
> I wonder what are the benefits of using Rally then? We can run whatever
>> we want by means of MCollective or Ansible. Is there something that could
>> help us? I don't know, maybe some dashboard integration with per test
>> results or running by tests by tag?
>
>
> Benefits are in the Rally framework, engine and integrated tooling, that
> are doing very hard things to provide simple interfaces for writing simple
> plugins that are emulating complicated test cases.
>
> The major benefits are next:
>
> *1) Generalization*
> 1.1) One tool with one reporting system and one output format for all
> kinds of testing strategies (functional, load, perf, scale, ...)
> 1.2) One set of plugins (code) that can be used to generate all kinds of
> testing strategies
> 1.3.) One API for all kinds of testing strategies
>
> *2) Simplicity *
> 2.1) Plugins are really simple to write, usually requires one method to be
> implemented
> 2.2) Auto discovery: adding plugins == add code in special (or specified)
> directory
>
> *3) Reusability & Data Driven approach: *
> 3.1) Split code (plugins) & tests cases (yaml files)
> 3.2) Test cases is mixture of different plugins
> 3.3) Plugins accept arguments
>
> *4) Integrated tooling*
> 4.1) All results are persisted in Rally DB and you can access it in any
> moment
> 4.2) Results can be exported in different formats (you can write even own
> plugins for simplifying integration)
> 4.3) Detailed HMTL reports with task results overview and trends
>
>
>
>
> Before switching Fuel from ostf to rally, I would like to see feature
>> parity comparison. It's very necessary to understand how much work we need
>> to spend to rewrite all our tests in rally way.
>
>
> Totally agree, let's do it.
>
>
> Best regards,
> Boris Pavlovic
>
>
>
> On Mon, Jun 27, 2016 at 8:58 AM, Vladimir Kuklin 
> wrote:
>
>> +1 to initial suggestion, but I guess we need to have a full feature
>> equality (e.g. HA tests for mysql and rabbitmq replication) before
>> switching to Rally.
>>
>> On Mon, Jun 27, 2016 at 6:17 PM, Sergii Golovatiuk <
>> sgolovat...@mirantis.com> wrote:
>>
>>> Hi,
>>>
>>> Before switching Fuel from ostf to rally, I would like to see feature
>>> parity comparison. It's very necessary to understand how much work we need
>>> to spend to rewrite all our tests in rally way.
>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Sergii Golovatiuk,
>>> Skype #golserge
>>> IRC #holser
>>>
>>> On Mon, Jun 27, 2016 at 4:32 PM, Alexander Kostrikov <
>>> akostri...@mirantis.com> wrote:
>>>
 Hello, everybody!
 Hello, Alex!
 >I thought Rally was more for benchmarking.  Wouldn't Tempest make
 more sense?
 Rally is a good tool with nice api/usage/extensibility.
 I really liked "up and running tests in 5 minutes" in Rally with clear
 picture of what I am doing.
 So, I 100% for a Rally as a QA.

 Another note:
 We will need to implement some HA tests, probably not in Rally.

 On Mon, Jun 27, 2016 at 4:57 PM, Andrey Kurilin 
 wrote:

>
>
> On Mon, Jun 27, 2016 at 4:46 PM, Igor Kalnitsky <
> ikalnit...@mirantis.com> wrote:
>
>>
>> > On Jun 27, 2016, at 16:23, Alex Schultz 
>> wrote:
>> >
>> > I thought Rally was more for benchmarking.  Wouldn't Tempest make
>> more sense?
>>
>> According to Rally wiki page [1], it seems they have a verification
>> layer (Tempest so far). Hm, I wonder does it mean we will need to rewrite
>> our scenarios for Tempest?
>>
>>
> Rally consists of two main components: Rally Task and Rally
> Verification. They are totally separated.
> Task component is fully pluggable and you can run there whatever you
> want in whatever you want way.
> Verification component is hardcoded now. It was designed for
> managing(install, configure) and launching(execute and store results)
> Tempest. But we have a spec to make this component pluggable too.
>
>
>> - igor
>>
>>
>> [1] https://wiki.openstack.org/wiki/Rally
>>
>> __
>> 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
>>
>
>
>
> --
> Best regards,
> Andrey Kurilin.
>
>
> __
> 

Re: [openstack-dev] [Fuel] Failed to build the bootstrap image

[Maksim Malchuk]

1. Show the logfile to see the bootstrap process is finished without any
errors.
2. It depends on the Fuel version, http://10.20.0.2/cobbler/boot in some
cases can't be seen through the web browser.
3. You shouldn't do anything only reboot the slave node. If fuel-bootstrap
executed correctly - your slave node should boot.
4. Also, there can be a problem in the VirtualBox settings, please don't
touch network/interfaces and use only fuel-virtualbox scripts to configure
them.


On Tue, Jun 28, 2016 at 6:28 PM, Alioune  wrote:

> Maksim,
> The bootstrap process woks fine without error but the slave can boot from
> network.
> I think that the issue is due TFTP process, it tries to reach
> http://10.20.0.2/cobbler/boot, I used my web browser but there is not
> directory named boot in cobbler folder.
> Should the bootstrap create this directory ?
>
> On 28 June 2016 at 15:59, Maksim Malchuk  wrote:
>
>> You can start build command with debug options enabled for example and
>> copy/paste output:
>>>
>>> fuel-bootstrap --verbose --debug build --activate
>>>
>>
>> Very bad idea to remove logfile, it's better to empty it not remove.
>>
>>  If you don't have the logfile, so recreate it with command:
>>
>>> touch /var/log/fuel-bootstrap-image-build.log
>>>
>>
>>
>> On Tue, Jun 28, 2016 at 4:09 PM, Alioune  wrote:
>>
>>> I've removed /var/log/fuel-bootstrap-image-build.log, created new
>>> bootstrap ubuntu again after setting proxy parameters and reboot.
>>> After the there is no /var/log/fuel-bootstrap-image-build.log create
>>> from the new bootstrap but slave doesn't boot correctly.
>>> Is there another way to detect slave nodes without creating image ?
>>> Regards,
>>> [image: Inline images 2]
>>>
>>> On 28 June 2016 at 13:34, Maksim Malchuk  wrote:
>>>
 You have an issue with connectivity from the Fuel master node to
 http://archive.ubuntu.com
 from the log:

> Command: debootstrap --include=ca-certificates,apt-transport-https 
> --verbose --no-check-gpg --arch=amd64 trusty 
> /tmp/tmp1K2haC.fuel-agent-image http://archive.ubuntu.com/ubuntu
> Exit code: 1
> Stdout: 'I: Retrieving Release \nE: Failed getting release file 
> http://archive.ubuntu.com/ubuntu/dists/trusty/Release\n'
> Stderr: ''
> Failed to execute command: Unexpected error while running command.
>
> please check your network connectivity, maybe firewall or nat settings.


 On Tue, Jun 28, 2016 at 2:28 PM, Alioune  wrote:

> Hi all,
> I tried to create ubuntu bootstrap using [0] but the slave can still
> not booting. You can find the bootstrap log following [1].
>
> Noticed that I've deleted the depot [2] from fuelmenu because it
> generated an error  "URL for repository mos is not accessible".
>
> Regards,
>
> [0] fuel-bootstrap build --ubuntu-release trusty  --activate
> [1]
> https://drive.google.com/folderview?id=0B-bfET74f0WZWE9Uc1lVOXJLcWM=sharing
> [2]  http://127.0.0.1:8080/ubuntu/x86_64/ mos8.0 main restricted
>
> On 27 June 2016 at 17:48, Maksim Malchuk 
> wrote:
>
>> Maybe the problem because you create the CentOS bootstrap which is
>> deprecated now.
>> If You really need the CentOS bootstrap, need to look into the
>> mentioned log file for this issue.
>>
>>
>> On Mon, Jun 27, 2016 at 6:33 PM, Alioune  wrote:
>>
>>> Thanks for your response,
>>>
>>> I've created and activated a new centOS bootstrap as suggested Sergi.
>>> Now the fuel-slave tries to boot from network but it fails at step
>>> TFTP http://10.20.0.2/cobbler/boot (unable to locate configuration
>>> file ).
>>> The bootstrap zip was generated in
>>> /tmp/a721103c-8693-4c58-985d-3f8223bdbc88.tar.gz, it seems that the 
>>> slave
>>> can not retreive the config files of the bootstrap.
>>> Are there additional config to do on the master side ?
>>> Regards
>>>
>>>  fuel-bootstrap list
>>>
>>> +--+--++
>>> | uuid | label
>>>  | status |
>>>
>>> +--+--++
>>> | a721103c-8693-4c58-985d-3f8223bdbc88 |
>>> a721103c-8693-4c58-985d-3f8223bdbc88 | active |
>>> | centos   | deprecated
>>>   ||
>>>
>>> +--+--++
>>>
>>> On 27 June 2016 at 16:58, Sergii Golovatiuk <
>>> sgolovat...@mirantis.com> wrote:
>>>
 Hi,

 I would suggest to build image from CLI using [0]. That will give
 more details to you.

Re: [openstack-dev] [Fuel] Failed to build the bootstrap image

[Alioune]

Maksim,
The bootstrap process woks fine without error but the slave can boot from
network.
I think that the issue is due TFTP process, it tries to reach
http://10.20.0.2/cobbler/boot, I used my web browser but there is not
directory named boot in cobbler folder.
Should the bootstrap create this directory ?

On 28 June 2016 at 15:59, Maksim Malchuk  wrote:

> You can start build command with debug options enabled for example and
> copy/paste output:
>>
>> fuel-bootstrap --verbose --debug build --activate
>>
>
> Very bad idea to remove logfile, it's better to empty it not remove.
>
>  If you don't have the logfile, so recreate it with command:
>
>> touch /var/log/fuel-bootstrap-image-build.log
>>
>
>
> On Tue, Jun 28, 2016 at 4:09 PM, Alioune  wrote:
>
>> I've removed /var/log/fuel-bootstrap-image-build.log, created new
>> bootstrap ubuntu again after setting proxy parameters and reboot.
>> After the there is no /var/log/fuel-bootstrap-image-build.log create from
>> the new bootstrap but slave doesn't boot correctly.
>> Is there another way to detect slave nodes without creating image ?
>> Regards,
>> [image: Inline images 2]
>>
>> On 28 June 2016 at 13:34, Maksim Malchuk  wrote:
>>
>>> You have an issue with connectivity from the Fuel master node to
>>> http://archive.ubuntu.com
>>> from the log:
>>>
 Command: debootstrap --include=ca-certificates,apt-transport-https 
 --verbose --no-check-gpg --arch=amd64 trusty 
 /tmp/tmp1K2haC.fuel-agent-image http://archive.ubuntu.com/ubuntu
 Exit code: 1
 Stdout: 'I: Retrieving Release \nE: Failed getting release file 
 http://archive.ubuntu.com/ubuntu/dists/trusty/Release\n'
 Stderr: ''
 Failed to execute command: Unexpected error while running command.

 please check your network connectivity, maybe firewall or nat settings.
>>>
>>>
>>> On Tue, Jun 28, 2016 at 2:28 PM, Alioune  wrote:
>>>
 Hi all,
 I tried to create ubuntu bootstrap using [0] but the slave can still
 not booting. You can find the bootstrap log following [1].

 Noticed that I've deleted the depot [2] from fuelmenu because it
 generated an error  "URL for repository mos is not accessible".

 Regards,

 [0] fuel-bootstrap build --ubuntu-release trusty  --activate
 [1]
 https://drive.google.com/folderview?id=0B-bfET74f0WZWE9Uc1lVOXJLcWM=sharing
 [2]  http://127.0.0.1:8080/ubuntu/x86_64/ mos8.0 main restricted

 On 27 June 2016 at 17:48, Maksim Malchuk  wrote:

> Maybe the problem because you create the CentOS bootstrap which is
> deprecated now.
> If You really need the CentOS bootstrap, need to look into the
> mentioned log file for this issue.
>
>
> On Mon, Jun 27, 2016 at 6:33 PM, Alioune  wrote:
>
>> Thanks for your response,
>>
>> I've created and activated a new centOS bootstrap as suggested Sergi.
>> Now the fuel-slave tries to boot from network but it fails at step
>> TFTP http://10.20.0.2/cobbler/boot (unable to locate configuration
>> file ).
>> The bootstrap zip was generated in
>> /tmp/a721103c-8693-4c58-985d-3f8223bdbc88.tar.gz, it seems that the slave
>> can not retreive the config files of the bootstrap.
>> Are there additional config to do on the master side ?
>> Regards
>>
>>  fuel-bootstrap list
>>
>> +--+--++
>> | uuid | label
>>  | status |
>>
>> +--+--++
>> | a721103c-8693-4c58-985d-3f8223bdbc88 |
>> a721103c-8693-4c58-985d-3f8223bdbc88 | active |
>> | centos   | deprecated
>> ||
>>
>> +--+--++
>>
>> On 27 June 2016 at 16:58, Sergii Golovatiuk > > wrote:
>>
>>> Hi,
>>>
>>> I would suggest to build image from CLI using [0]. That will give
>>> more details to you.
>>>
>>> [0]
>>> http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/bootstrap/bootstrap_builder.html
>>>
>>> --
>>> Best regards,
>>> Sergii Golovatiuk,
>>> Skype #golserge
>>> IRC #holser
>>>
>>> On Mon, Jun 27, 2016 at 3:20 PM, Maksim Malchuk <
>>> mmalc...@mirantis.com> wrote:
>>>
 Hi,

 The error about an internet connection is the only common case. You
 should check the actual error in the log file
 /var/log/fuel-bootstrap-image-build.log.
 You can also share this file with us via any public service
 (GoogleDrive, DropBox, etc) and we will check it for 

Re: [openstack-dev] [Fuel] Deprecate fuel-upgrade repository

[Vladimir Kozhukalov]

This patch [1] is a part of project retirement procedure [2]. Review is
welcome.

[1] https://review.openstack.org/#/c/335085/
[2] http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project

Vladimir Kozhukalov

On Tue, Jun 28, 2016 at 1:41 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:

> Dear colleagues,
>
> Please be informed that fuel-upgrade [1] repository is going to be
> deprecated. We used to develop Fuel admin node upgrade scenarios in this
> repo, but now all upgrade related stuff is in fuel-octane [2] repo. So,
> fuel-upgrade is to be removed from the list of official Fuel repos [3].
> Fuel-upgrade will stay available for a while perhaps for about a year or so
> in case some of Fuel users want to build upgrade tarball.
>
>
> [1] https://github.com/openstack/fuel-upgrade
> [2] https://github.com/openstack/fuel-octane
> [3] https://review.openstack.org/#/c/334903/
>
> Vladimir Kozhukalov
>
__
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] [Fuel] Failed to build the bootstrap image

[Maksim Malchuk]

You can start build command with debug options enabled for example and
copy/paste output:
>
> fuel-bootstrap --verbose --debug build --activate
>

Very bad idea to remove logfile, it's better to empty it not remove.

 If you don't have the logfile, so recreate it with command:

> touch /var/log/fuel-bootstrap-image-build.log
>


On Tue, Jun 28, 2016 at 4:09 PM, Alioune  wrote:

> I've removed /var/log/fuel-bootstrap-image-build.log, created new
> bootstrap ubuntu again after setting proxy parameters and reboot.
> After the there is no /var/log/fuel-bootstrap-image-build.log create from
> the new bootstrap but slave doesn't boot correctly.
> Is there another way to detect slave nodes without creating image ?
> Regards,
> [image: Inline images 2]
>
> On 28 June 2016 at 13:34, Maksim Malchuk  wrote:
>
>> You have an issue with connectivity from the Fuel master node to
>> http://archive.ubuntu.com
>> from the log:
>>
>>> Command: debootstrap --include=ca-certificates,apt-transport-https 
>>> --verbose --no-check-gpg --arch=amd64 trusty 
>>> /tmp/tmp1K2haC.fuel-agent-image http://archive.ubuntu.com/ubuntu
>>> Exit code: 1
>>> Stdout: 'I: Retrieving Release \nE: Failed getting release file 
>>> http://archive.ubuntu.com/ubuntu/dists/trusty/Release\n'
>>> Stderr: ''
>>> Failed to execute command: Unexpected error while running command.
>>>
>>> please check your network connectivity, maybe firewall or nat settings.
>>
>>
>> On Tue, Jun 28, 2016 at 2:28 PM, Alioune  wrote:
>>
>>> Hi all,
>>> I tried to create ubuntu bootstrap using [0] but the slave can still not
>>> booting. You can find the bootstrap log following [1].
>>>
>>> Noticed that I've deleted the depot [2] from fuelmenu because it
>>> generated an error  "URL for repository mos is not accessible".
>>>
>>> Regards,
>>>
>>> [0] fuel-bootstrap build --ubuntu-release trusty  --activate
>>> [1]
>>> https://drive.google.com/folderview?id=0B-bfET74f0WZWE9Uc1lVOXJLcWM=sharing
>>> [2]  http://127.0.0.1:8080/ubuntu/x86_64/ mos8.0 main restricted
>>>
>>> On 27 June 2016 at 17:48, Maksim Malchuk  wrote:
>>>
 Maybe the problem because you create the CentOS bootstrap which is
 deprecated now.
 If You really need the CentOS bootstrap, need to look into the
 mentioned log file for this issue.


 On Mon, Jun 27, 2016 at 6:33 PM, Alioune  wrote:

> Thanks for your response,
>
> I've created and activated a new centOS bootstrap as suggested Sergi.
> Now the fuel-slave tries to boot from network but it fails at step
> TFTP http://10.20.0.2/cobbler/boot (unable to locate configuration
> file ).
> The bootstrap zip was generated in
> /tmp/a721103c-8693-4c58-985d-3f8223bdbc88.tar.gz, it seems that the slave
> can not retreive the config files of the bootstrap.
> Are there additional config to do on the master side ?
> Regards
>
>  fuel-bootstrap list
>
> +--+--++
> | uuid | label
>| status |
>
> +--+--++
> | a721103c-8693-4c58-985d-3f8223bdbc88 |
> a721103c-8693-4c58-985d-3f8223bdbc88 | active |
> | centos   | deprecated
> ||
>
> +--+--++
>
> On 27 June 2016 at 16:58, Sergii Golovatiuk 
> wrote:
>
>> Hi,
>>
>> I would suggest to build image from CLI using [0]. That will give
>> more details to you.
>>
>> [0]
>> http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/bootstrap/bootstrap_builder.html
>>
>> --
>> Best regards,
>> Sergii Golovatiuk,
>> Skype #golserge
>> IRC #holser
>>
>> On Mon, Jun 27, 2016 at 3:20 PM, Maksim Malchuk <
>> mmalc...@mirantis.com> wrote:
>>
>>> Hi,
>>>
>>> The error about an internet connection is the only common case. You
>>> should check the actual error in the log file
>>> /var/log/fuel-bootstrap-image-build.log.
>>> You can also share this file with us via any public service
>>> (GoogleDrive, DropBox, etc) and we will check it for you.
>>>
>>> On Mon, Jun 27, 2016 at 4:08 PM, Maksim Malchuk <
>>> mmalc...@mirantis.com> wrote:
>>>
 Hi,

 The error about an internet connection is the only common case. You
 should check the actual error in the log file
 /var/log/fuel-bootstrap-image-build.log.
 You can also share this file with us via any public service
 (GoogleDrive, DropBox, etc) and we will check it for you.


 On Mon, Jun 27, 2016 at 1:43 

Re: [openstack-dev] [Fuel] Failed to build the bootstrap image

[Alioune]

I've removed /var/log/fuel-bootstrap-image-build.log, created new bootstrap
ubuntu again after setting proxy parameters and reboot.
After the there is no /var/log/fuel-bootstrap-image-build.log create from
the new bootstrap but slave doesn't boot correctly.
Is there another way to detect slave nodes without creating image ?
Regards,
[image: Inline images 2]

On 28 June 2016 at 13:34, Maksim Malchuk  wrote:

> You have an issue with connectivity from the Fuel master node to
> http://archive.ubuntu.com
> from the log:
>
>> Command: debootstrap --include=ca-certificates,apt-transport-https --verbose 
>> --no-check-gpg --arch=amd64 trusty /tmp/tmp1K2haC.fuel-agent-image 
>> http://archive.ubuntu.com/ubuntu
>> Exit code: 1
>> Stdout: 'I: Retrieving Release \nE: Failed getting release file 
>> http://archive.ubuntu.com/ubuntu/dists/trusty/Release\n'
>> Stderr: ''
>> Failed to execute command: Unexpected error while running command.
>>
>> please check your network connectivity, maybe firewall or nat settings.
>
>
> On Tue, Jun 28, 2016 at 2:28 PM, Alioune  wrote:
>
>> Hi all,
>> I tried to create ubuntu bootstrap using [0] but the slave can still not
>> booting. You can find the bootstrap log following [1].
>>
>> Noticed that I've deleted the depot [2] from fuelmenu because it
>> generated an error  "URL for repository mos is not accessible".
>>
>> Regards,
>>
>> [0] fuel-bootstrap build --ubuntu-release trusty  --activate
>> [1]
>> https://drive.google.com/folderview?id=0B-bfET74f0WZWE9Uc1lVOXJLcWM=sharing
>> [2]  http://127.0.0.1:8080/ubuntu/x86_64/ mos8.0 main restricted
>>
>> On 27 June 2016 at 17:48, Maksim Malchuk  wrote:
>>
>>> Maybe the problem because you create the CentOS bootstrap which is
>>> deprecated now.
>>> If You really need the CentOS bootstrap, need to look into the mentioned
>>> log file for this issue.
>>>
>>>
>>> On Mon, Jun 27, 2016 at 6:33 PM, Alioune  wrote:
>>>
 Thanks for your response,

 I've created and activated a new centOS bootstrap as suggested Sergi.
 Now the fuel-slave tries to boot from network but it fails at step TFTP
 http://10.20.0.2/cobbler/boot (unable to locate configuration file ).
 The bootstrap zip was generated in
 /tmp/a721103c-8693-4c58-985d-3f8223bdbc88.tar.gz, it seems that the slave
 can not retreive the config files of the bootstrap.
 Are there additional config to do on the master side ?
 Regards

  fuel-bootstrap list

 +--+--++
 | uuid | label
| status |

 +--+--++
 | a721103c-8693-4c58-985d-3f8223bdbc88 |
 a721103c-8693-4c58-985d-3f8223bdbc88 | active |
 | centos   | deprecated
   ||

 +--+--++

 On 27 June 2016 at 16:58, Sergii Golovatiuk 
 wrote:

> Hi,
>
> I would suggest to build image from CLI using [0]. That will give more
> details to you.
>
> [0]
> http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/bootstrap/bootstrap_builder.html
>
> --
> Best regards,
> Sergii Golovatiuk,
> Skype #golserge
> IRC #holser
>
> On Mon, Jun 27, 2016 at 3:20 PM, Maksim Malchuk  > wrote:
>
>> Hi,
>>
>> The error about an internet connection is the only common case. You
>> should check the actual error in the log file
>> /var/log/fuel-bootstrap-image-build.log.
>> You can also share this file with us via any public service
>> (GoogleDrive, DropBox, etc) and we will check it for you.
>>
>> On Mon, Jun 27, 2016 at 4:08 PM, Maksim Malchuk <
>> mmalc...@mirantis.com> wrote:
>>
>>> Hi,
>>>
>>> The error about an internet connection is the only common case. You
>>> should check the actual error in the log file
>>> /var/log/fuel-bootstrap-image-build.log.
>>> You can also share this file with us via any public service
>>> (GoogleDrive, DropBox, etc) and we will check it for you.
>>>
>>>
>>> On Mon, Jun 27, 2016 at 1:43 PM, Alioune 
>>> wrote:
>>>
 hi all,

 I'm trying to install fuel in VirtualBox, the fuel master is
 correctly running but I'm receiving the this error on the fuel GUI:

 WARNING: Failed to build the bootstrap image, see
 /var/log/fuel-bootstrap-image-build.log for details.
 Perhaps your Internet connection is broken. Please fix the problem
 and run `fuel-bootstrap build --activate`.
 While you don't activate any bootstrap - 

Re: [openstack-dev] [Fuel] Failed to build the bootstrap image

[Maksim Malchuk]

You have an issue with connectivity from the Fuel master node to
http://archive.ubuntu.com
from the log:

> Command: debootstrap --include=ca-certificates,apt-transport-https --verbose 
> --no-check-gpg --arch=amd64 trusty /tmp/tmp1K2haC.fuel-agent-image 
> http://archive.ubuntu.com/ubuntu
> Exit code: 1
> Stdout: 'I: Retrieving Release \nE: Failed getting release file 
> http://archive.ubuntu.com/ubuntu/dists/trusty/Release\n'
> Stderr: ''
> Failed to execute command: Unexpected error while running command.
>
> please check your network connectivity, maybe firewall or nat settings.


On Tue, Jun 28, 2016 at 2:28 PM, Alioune  wrote:

> Hi all,
> I tried to create ubuntu bootstrap using [0] but the slave can still not
> booting. You can find the bootstrap log following [1].
>
> Noticed that I've deleted the depot [2] from fuelmenu because it generated
> an error  "URL for repository mos is not accessible".
>
> Regards,
>
> [0] fuel-bootstrap build --ubuntu-release trusty  --activate
> [1]
> https://drive.google.com/folderview?id=0B-bfET74f0WZWE9Uc1lVOXJLcWM=sharing
> [2]  http://127.0.0.1:8080/ubuntu/x86_64/ mos8.0 main restricted
>
> On 27 June 2016 at 17:48, Maksim Malchuk  wrote:
>
>> Maybe the problem because you create the CentOS bootstrap which is
>> deprecated now.
>> If You really need the CentOS bootstrap, need to look into the mentioned
>> log file for this issue.
>>
>>
>> On Mon, Jun 27, 2016 at 6:33 PM, Alioune  wrote:
>>
>>> Thanks for your response,
>>>
>>> I've created and activated a new centOS bootstrap as suggested Sergi.
>>> Now the fuel-slave tries to boot from network but it fails at step TFTP
>>> http://10.20.0.2/cobbler/boot (unable to locate configuration file ).
>>> The bootstrap zip was generated in
>>> /tmp/a721103c-8693-4c58-985d-3f8223bdbc88.tar.gz, it seems that the slave
>>> can not retreive the config files of the bootstrap.
>>> Are there additional config to do on the master side ?
>>> Regards
>>>
>>>  fuel-bootstrap list
>>>
>>> +--+--++
>>> | uuid | label
>>>  | status |
>>>
>>> +--+--++
>>> | a721103c-8693-4c58-985d-3f8223bdbc88 |
>>> a721103c-8693-4c58-985d-3f8223bdbc88 | active |
>>> | centos   | deprecated
>>>   ||
>>>
>>> +--+--++
>>>
>>> On 27 June 2016 at 16:58, Sergii Golovatiuk 
>>> wrote:
>>>
 Hi,

 I would suggest to build image from CLI using [0]. That will give more
 details to you.

 [0]
 http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/bootstrap/bootstrap_builder.html

 --
 Best regards,
 Sergii Golovatiuk,
 Skype #golserge
 IRC #holser

 On Mon, Jun 27, 2016 at 3:20 PM, Maksim Malchuk 
 wrote:

> Hi,
>
> The error about an internet connection is the only common case. You
> should check the actual error in the log file
> /var/log/fuel-bootstrap-image-build.log.
> You can also share this file with us via any public service
> (GoogleDrive, DropBox, etc) and we will check it for you.
>
> On Mon, Jun 27, 2016 at 4:08 PM, Maksim Malchuk  > wrote:
>
>> Hi,
>>
>> The error about an internet connection is the only common case. You
>> should check the actual error in the log file
>> /var/log/fuel-bootstrap-image-build.log.
>> You can also share this file with us via any public service
>> (GoogleDrive, DropBox, etc) and we will check it for you.
>>
>>
>> On Mon, Jun 27, 2016 at 1:43 PM, Alioune  wrote:
>>
>>> hi all,
>>>
>>> I'm trying to install fuel in VirtualBox, the fuel master is
>>> correctly running but I'm receiving the this error on the fuel GUI:
>>>
>>> WARNING: Failed to build the bootstrap image, see
>>> /var/log/fuel-bootstrap-image-build.log for details.
>>> Perhaps your Internet connection is broken. Please fix the problem
>>> and run `fuel-bootstrap build --activate`.
>>> While you don't activate any bootstrap - new nodes cannot be
>>> discovered and added to cluster.
>>> For more information please visit
>>> https://docs.mirantis.com/openstack/fuel/fuel-master/
>>>
>>> The fuel server has access to internet even though it could not find
>>> depots during install, I ran "yum update" and reboot but I still get 
>>> this
>>> error.
>>> I configured a fuel-slave server boot from network attached to the
>>> fuel-master but the process failed also.
>>> Any help please to solve this ?
>>>
>>> Regards,
>>>
>>>

Re: [openstack-dev] [Fuel] Failed to build the bootstrap image

[Alioune]

Hi all,
I tried to create ubuntu bootstrap using [0] but the slave can still not
booting. You can find the bootstrap log following [1].

Noticed that I've deleted the depot [2] from fuelmenu because it generated
an error  "URL for repository mos is not accessible".

Regards,

[0] fuel-bootstrap build --ubuntu-release trusty  --activate
[1]
https://drive.google.com/folderview?id=0B-bfET74f0WZWE9Uc1lVOXJLcWM=sharing
[2]  http://127.0.0.1:8080/ubuntu/x86_64/ mos8.0 main restricted

On 27 June 2016 at 17:48, Maksim Malchuk  wrote:

> Maybe the problem because you create the CentOS bootstrap which is
> deprecated now.
> If You really need the CentOS bootstrap, need to look into the mentioned
> log file for this issue.
>
>
> On Mon, Jun 27, 2016 at 6:33 PM, Alioune  wrote:
>
>> Thanks for your response,
>>
>> I've created and activated a new centOS bootstrap as suggested Sergi.
>> Now the fuel-slave tries to boot from network but it fails at step TFTP
>> http://10.20.0.2/cobbler/boot (unable to locate configuration file ).
>> The bootstrap zip was generated in
>> /tmp/a721103c-8693-4c58-985d-3f8223bdbc88.tar.gz, it seems that the slave
>> can not retreive the config files of the bootstrap.
>> Are there additional config to do on the master side ?
>> Regards
>>
>>  fuel-bootstrap list
>>
>> +--+--++
>> | uuid | label
>>  | status |
>>
>> +--+--++
>> | a721103c-8693-4c58-985d-3f8223bdbc88 |
>> a721103c-8693-4c58-985d-3f8223bdbc88 | active |
>> | centos   | deprecated
>> ||
>>
>> +--+--++
>>
>> On 27 June 2016 at 16:58, Sergii Golovatiuk 
>> wrote:
>>
>>> Hi,
>>>
>>> I would suggest to build image from CLI using [0]. That will give more
>>> details to you.
>>>
>>> [0]
>>> http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/bootstrap/bootstrap_builder.html
>>>
>>> --
>>> Best regards,
>>> Sergii Golovatiuk,
>>> Skype #golserge
>>> IRC #holser
>>>
>>> On Mon, Jun 27, 2016 at 3:20 PM, Maksim Malchuk 
>>> wrote:
>>>
 Hi,

 The error about an internet connection is the only common case. You
 should check the actual error in the log file
 /var/log/fuel-bootstrap-image-build.log.
 You can also share this file with us via any public service
 (GoogleDrive, DropBox, etc) and we will check it for you.

 On Mon, Jun 27, 2016 at 4:08 PM, Maksim Malchuk 
 wrote:

> Hi,
>
> The error about an internet connection is the only common case. You
> should check the actual error in the log file
> /var/log/fuel-bootstrap-image-build.log.
> You can also share this file with us via any public service
> (GoogleDrive, DropBox, etc) and we will check it for you.
>
>
> On Mon, Jun 27, 2016 at 1:43 PM, Alioune  wrote:
>
>> hi all,
>>
>> I'm trying to install fuel in VirtualBox, the fuel master is
>> correctly running but I'm receiving the this error on the fuel GUI:
>>
>> WARNING: Failed to build the bootstrap image, see
>> /var/log/fuel-bootstrap-image-build.log for details.
>> Perhaps your Internet connection is broken. Please fix the problem
>> and run `fuel-bootstrap build --activate`.
>> While you don't activate any bootstrap - new nodes cannot be
>> discovered and added to cluster.
>> For more information please visit
>> https://docs.mirantis.com/openstack/fuel/fuel-master/
>>
>> The fuel server has access to internet even though it could not find
>> depots during install, I ran "yum update" and reboot but I still get this
>> error.
>> I configured a fuel-slave server boot from network attached to the
>> fuel-master but the process failed also.
>> Any help please to solve this ?
>>
>> Regards,
>>
>>
>> __
>> 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
>>
>>
>
>
> --
> Best Regards,
> Maksim Malchuk,
> Senior DevOps Engineer,
> MOS: Product Engineering,
> Mirantis, Inc
> 
>



 --
 Best Regards,
 Maksim Malchuk,
 Senior DevOps Engineer,
 MOS: Product Engineering,
 Mirantis, Inc
 


 __
 OpenStack Development Mailing List 

Re: [openstack-dev] [Fuel] - Nominate Maksim Malchuk to Fuel Library Core

[Adam Heczko]

Although I'm not Fuel core, +1 from me to Maksim. Maksim is not only
excellent engineer but also very friendly and helpful folk.

On Tue, Jun 28, 2016 at 12:19 PM, Georgy Kibardin 
wrote:

> +1
>
> On Tue, Jun 28, 2016 at 1:12 PM, Kyrylo Galanov 
> wrote:
>
>> +1
>>
>> On Tue, Jun 28, 2016 at 1:16 AM, Matthew Mosesohn > > wrote:
>>
>>> +1. Maksim is an excellent reviewer.
>>>
>>> On Mon, Jun 27, 2016 at 6:06 PM, Alex Schultz 
>>> wrote:
>>> > +1
>>> >
>>> > On Mon, Jun 27, 2016 at 9:04 AM, Bogdan Dobrelya <
>>> bdobre...@mirantis.com>
>>> > wrote:
>>> >>
>>> >> On 06/27/2016 04:54 PM, Sergii Golovatiuk wrote:
>>> >> > I am very sorry for sending without subject. I am adding subject to
>>> >> > voting and my +1
>>> >>
>>> >> +1 from my side!
>>> >>
>>> >> >
>>> >> > --
>>> >> > Best regards,
>>> >> > Sergii Golovatiuk,
>>> >> > Skype #golserge
>>> >> > IRC #holser
>>> >> >
>>> >> > On Mon, Jun 27, 2016 at 4:42 PM, Sergii Golovatiuk
>>> >> > > wrote:
>>> >> >
>>> >> > Hi,
>>> >> >
>>> >> > I would like to nominate Maksim Malchuk to Fuel-Library Core
>>> team.
>>> >> > He’s been doing a great job so far [0]. He’s #2 reviewer and #2
>>> >> > contributor with 28 commits for last 90 days [1][2].
>>> >> >
>>> >> > Fuelers, please vote with +1/-1 for approval/objection. Voting
>>> will
>>> >> > be open until July of 4th. This will go forward after voting is
>>> >> > closed if there are no objections.
>>> >> >
>>> >> > Overall contribution:
>>> >> > [0] http://stackalytics.com/?user_id=mmalchuk
>>> >> > Fuel library contribution for last 90 days:
>>> >> > [1]
>>> >> > 
>>> http://stackalytics.com/report/contribution/fuel-library/90
>>> >> > http://stackalytics.com/report/users/mmalchuk
>>> >> > List of reviews:
>>> >> > [2]
>>> >> >
>>> https://review.openstack.org/#/q/reviewer:%22Maksim+Malchuk%22+status:merged,n,z
>>> >> > --
>>> >> > Best regards,
>>> >> > Sergii Golovatiuk,
>>> >> > Skype #golserge
>>> >> > IRC #holser
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> __
>>> >> > 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
>>> >> >
>>> >>
>>> >>
>>> >> --
>>> >> Best regards,
>>> >> Bogdan Dobrelya,
>>> >> Irc #bogdando
>>> >>
>>> >>
>>> __
>>> >> 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
>>>
>>
>>
>> __
>> 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
>
>


-- 
Adam Heczko
Security Engineer @ Mirantis Inc.
__
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