Re: [openstack-dev] [fuel-virtualbox] Nominate Serhii Ovsianikov to fuel-virtualbox core
As there are no objections so, please welcome Serhii as he's just joined fuel-virtualbox Core Team! On Thu, Sep 8, 2016 at 12:01 PM, Sergey Kulanov wrote: > +1 > > 2016-09-08 11:12 GMT+03:00 Vladimir Kozhukalov : > >> +1 >> >> Vladimir Kozhukalov >> >> On Thu, Sep 8, 2016 at 1:55 AM, Maksim Malchuk >> wrote: >> >>> Hello, >>> >>> I would like to nominate Serhii Ovsianikov to fuel-virtualbox core due >>> to his significant contribution to the project [1] and [2]. He is the >>> second reviewer and for the last half of the year [2] acts as an unoficial >>> QA in the fuel-virtualbox project. >>> >>> [1] http://stackalytics.com/?user_id=sovsianikov&project_typ >>> e=all&release=all&metric=marks&module=fuel-virtualbox >>> [2] http://stackalytics.com/report/contribution/fuel-virtualbox/180 >>> >>> -- >>> 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.op >>> enstack.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:unsubscrib >> e >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > > -- > Sergey > DevOps Engineer > IRC: SergK > Skype: Sergey_kul > > __ > OpenStack Development Mailing 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-library] Nominate Stanislaw Bogatkin to fuel-library core
As there are no objections so, please welcome Stanislaw as he's just joined fuel-library Core Team! On Tue, Sep 13, 2016 at 3:07 PM, Aleksey Kasatkin wrote: > +1 > > > Aleksey Kasatkin > > > On Mon, Sep 12, 2016 at 5:01 PM, Alex Schultz wrote: > >> +1 >> >> On Wed, Sep 7, 2016 at 5:07 PM, Maksim Malchuk >> wrote: >> > Hello, >> > >> > I would like to nominate Stanislaw Bogatkin to fuel-library core due to >> his >> > significant contribution to the project [1] and [2]. He is one of the >> top >> > reviewers and contributors in the project. >> > >> > [1] >> > http://stackalytics.com/?user_id=sbogatkin&project_type=all&; >> release=all&metric=marks&module=fuel-library >> > [2] http://stackalytics.com/report/contribution/fuel-library/90 >> > >> > -- >> > 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.op >> enstack.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: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 > > -- 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] Nominate Ilya Kutukov for fuel-plugins-core
+1 On Thu, Sep 8, 2016 at 11:54 AM, Igor Kalnitsky wrote: > Hey Fuelers, > > I'd like to nominate Ilya for joining fuel-plugins-core group. He's a > top contributor by both reviews [1] and commits [2] over the past > release cycle. Fuel cores, please share your votes. > > - Igor > > [1] http://stackalytics.com/?module=fuel-plugins&release= > newton&metric=marks > [2] http://stackalytics.com/?module=fuel-plugins&release= > newton&metric=commits > > __ > OpenStack Development Mailing 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
[openstack-dev] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core
Hello, I would like to nominate Stanislaw Bogatkin to fuel-library core due to his significant contribution to the project [1] and [2]. He is one of the top reviewers and contributors in the project. [1] http://stackalytics.com/?user_id=sbogatkin&project_type=all&release=all&metric=marks&module=fuel-library [2] http://stackalytics.com/report/contribution/fuel-library/90 -- 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
[openstack-dev] [fuel-virtualbox] Nominate Serhii Ovsianikov to fuel-virtualbox core
Hello, I would like to nominate Serhii Ovsianikov to fuel-virtualbox core due to his significant contribution to the project [1] and [2]. He is the second reviewer and for the last half of the year [2] acts as an unoficial QA in the fuel-virtualbox project. [1] http://stackalytics.com/?user_id=sovsianikov&project_type=all&release=all&metric=marks&module=fuel-virtualbox [2] http://stackalytics.com/report/contribution/fuel-virtualbox/180 -- 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] Common fuel-core group for all Fuel projects
I want to clarify my previous reply +1 but the new fuel-core would be a small group of the cores who are fully involved in the whole Fuel project. On Mon, Sep 5, 2016 at 7:22 PM, Alexey Stepanov wrote: > -1 > This is seriously dangerous idea: core-reviewer in fuel-qa does not mean > exact skills for +2/W on fuel-octane, for example. Sometimes, because of > limited time, reviewer will press +W without understanding patch detail. In > repo, which he knows, he can fix issue later by itself, but only of he > really knows what he doing. > > пн, 5 сент. 2016 г., 19:14 Maksim Malchuk : > >> -1 >> My vision - we should have something like super-core group with a smaller >> number of the current core guys. >> This is because a lot of current core guys were switched to the other >> projects and already out of the scope. >> Such guys still can be cores in their former projects and can help >> sometimes, but only several guys can drive the Fuel. >> >> P.S. we always can nominate new cores to the specific project >> individually if you don't like the super-core group idea. >> >> On Mon, Sep 5, 2016 at 6:39 PM, Andrew Maksimov >> wrote: >> >>> +1 >>> This is a good proposal, I also think we should have single fuel-core >>> group for all repos. In real life core reviewers won't set +2 or merge to >>> repos with which they are not familiar with. >>> >>> Regards, >>> Andrey Maximov >>> >>> On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov < >>> vkozhuka...@mirantis.com> wrote: >>> >>>> Dear colleagues, >>>> >>>> I'd like to suggest to use common fuel-core group for all Fuel projects >>>> instead of having separate independent 'by-project' core groups like >>>> 'fuel-astute-core' or 'fuel-agent-core'. >>>> >>>> Pros: >>>> 1) It will be easier to access core members (timezone and holiday >>>> tolerance) >>>> 2) It will be easier to manage single core group (promote new members, >>>> remove not active members) >>>> >>>> Cons: >>>> 1) Less of flexibility. Permissions will be the same for all core >>>> reviewers in all Fuel projects. >>>> >>>> What do you think? >>>> >>>> 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 >>> >>> >> >> >> -- >> 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 >> > > __ > OpenStack Development Mailing 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] Common fuel-core group for all Fuel projects
-1 My vision - we should have something like super-core group with a smaller number of the current core guys. This is because a lot of current core guys were switched to the other projects and already out of the scope. Such guys still can be cores in their former projects and can help sometimes, but only several guys can drive the Fuel. P.S. we always can nominate new cores to the specific project individually if you don't like the super-core group idea. On Mon, Sep 5, 2016 at 6:39 PM, Andrew Maksimov wrote: > +1 > This is a good proposal, I also think we should have single fuel-core > group for all repos. In real life core reviewers won't set +2 or merge to > repos with which they are not familiar with. > > Regards, > Andrey Maximov > > On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov < > vkozhuka...@mirantis.com> wrote: > >> Dear colleagues, >> >> I'd like to suggest to use common fuel-core group for all Fuel projects >> instead of having separate independent 'by-project' core groups like >> 'fuel-astute-core' or 'fuel-agent-core'. >> >> Pros: >> 1) It will be easier to access core members (timezone and holiday >> tolerance) >> 2) It will be easier to manage single core group (promote new members, >> remove not active members) >> >> Cons: >> 1) Less of flexibility. Permissions will be the same for all core >> reviewers in all Fuel projects. >> >> What do you think? >> >> Vladimir Kozhukalov >> >> >> __ >> 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 > > -- 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
Although today is not the 31 Aug and we have a lack of core-reviewers in the fuel-library I would like to speed up the process a little. And as there are no objections so, please welcome Denis as he's just joined fuel-library Core Team! On Mon, Aug 29, 2016 at 3:15 PM, Vladimir Kozhukalov < vkozhuka...@mirantis.com> wrote: > Although I am not a core in fuel-library, I am voting +1. > > Vladimir Kozhukalov > > On Fri, Aug 26, 2016 at 1:27 PM, Ivan Berezovskiy < > iberezovs...@mirantis.com> wrote: > >> +1, great job! >> >> 2016-08-26 10:33 GMT+03:00 Bogdan Dobrelya : >> >>> +1 >>> >>> On 25.08.2016 21:08, Stanislaw Bogatkin wrote: >>> > +1 >>> > >>> > On Thu, Aug 25, 2016 at 12:08 PM, Aleksandr Didenko >>> > mailto:adide...@mirantis.com>> wrote: >>> > >>> > +1 >>> > >>> > On Thu, Aug 25, 2016 at 9:35 AM, Sergey Vasilenko >>> > mailto:svasile...@mirantis.com>> wrote: >>> > >>> > +1 >>> > >>> > >>> > /sv >>> > >>> > >>> > ___ >>> ___ >>> > 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/opensta >>> ck-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/opensta >>> ck-dev> >>> > >>> > >>> > >>> > ___ >>> ___ >>> > 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 >>> > <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.op >>> enstack.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.op >>> enstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> >> >> -- >> Thanks, Ivan Berezovskiy >> MOS Puppet Team Lead >> at Mirantis <https://www.mirantis.com/> >> >> slack: iberezovskiy >> skype: bouhforever >> phone: + 7-960-343-42-46 >> >> >> >> __ >> 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 > > -- 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
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] - Nominate Maksim Malchuk to Fuel Library Core
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 >>>>> >> > mailto:sgolovat...@mirantis.com>> >>>>> 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/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 >>>>> >> > >>>>> >> >>>>> >> >>>>> >
Re: [openstack-dev] [Fuel] Failed to build the bootstrap image
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&usp=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
Re: [openstack-dev] [Fuel] Failed to build the bootstrap image
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&usp=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 Golovatiu
Re: [openstack-dev] [Fuel] Failed to build the bootstrap image
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&usp=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 >>>>>>> cor
Re: [openstack-dev] [Fuel] Failed to build the bootstrap image
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, >
Re: [openstack-dev] [Fuel] Failed to build the bootstrap image
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 (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
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 __ OpenStack Development Mailing 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] [puppet] Proposing Ivan Berezovskiy for puppet-openstack-core
Ivan, Great job! Congrats! +1 On Fri, May 20, 2016 at 5:29 PM, Anastasia Urlapova wrote: > +1 > > On Fri, May 20, 2016 at 5:07 PM, Ivan Berezovskiy < > iberezovs...@mirantis.com> wrote: > >> Thank you all for the trust! I'll do my best :) >> >> 2016-05-19 18:57 GMT+03:00 Alex Schultz : >> >>> +1 great job Ivan >>> >>> On Thu, May 19, 2016 at 8:32 AM, Matt Fischer >>> wrote: >>> >>>> +1 from me! >>>> >>>> On Thu, May 19, 2016 at 8:17 AM, Emilien Macchi >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> I don't need to introduce Ivan Berezovskiy (iberezovskiy on IRC), he's >>>>> been doing tremendous work in Puppet OpenStack over the last months, >>>>> in a regular way. >>>>> >>>>> Some highlights about his contributions: >>>>> * Fantastic work on puppet-oslo! I really mean it... Thanks to you and >>>>> others, we have now consistency for Oslo parameters in our modules. >>>>> * Excellent quality of code in general and in reviews. >>>>> * Full understanding of our process (code style, release notes, CI, >>>>> doc, etc). >>>>> * Very often, he helps with CI things (Fuel or Puppet OpenStack CI). >>>>> * Constant presence on IRC meetings and in our channel where he never >>>>> hesitate to give support. >>>>> >>>>> I would like to propose him part of our Puppet OpenStack core team, as >>>>> usual please -1/+1. >>>>> >>>>> Thanks Ivan for your hard work, keep going! >>>>> -- >>>>> 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 >>>>> >>>> >>>> >>>> >>>> __ >>>> OpenStack Development Mailing 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 >>> >>> >> >> >> -- >> Thanks, Ivan Berezovskiy >> MOS Puppet Team Lead >> at Mirantis <https://www.mirantis.com/> >> >> slack: iberezovskiy >> skype: bouhforever >> phone: + 7-960-343-42-46 >> >> >> __ >> OpenStack Development Mailing 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, 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][Fuel-Library] Nominating Matthew Mosesohn for Fuel Library Core
Matthew, congrats! On Fri, Mar 11, 2016 at 10:59 PM, Sergii Golovatiuk < sgolovat...@mirantis.com> wrote: > Hi, > > Personally, I give my +2 to Matthew without any doubts. Matthew reviews > has a lot of technical details and guidances. As always he is bright > helping people over IRC or mailing list. > > Please welcome a new member of fuel-library-core group. > > -- > Best regards, > Sergii Golovatiuk, > Skype #golserge > IRC #holser > > On Wed, Mar 2, 2016 at 5:44 PM, Aleksandr Didenko > wrote: > >> +1 for Michael Polenchuk >> >> On Wed, Mar 2, 2016 at 5:33 PM, Fedor Zhadaev >> wrote: >> >>> +1 for Michael :) >>> >>> ср, 2 мар 2016, 17:50 Matthew Mosesohn : >>> >>>> Hi all, >>>> >>>> Thank you for the nominations and +1s. I would like to propose Michael >>>> Polenchuk to add as a maintainer to fuel-library to take my spot when >>>> I leave the maintainers list. >>>> >>>> Best Regards, >>>> Matthew Mosesohn >>>> >>>> On Fri, Feb 26, 2016 at 3:54 PM, Kyrylo Galanov >>>> wrote: >>>> > Finally! +2 ! >>>> > >>>> > On Fri, Feb 26, 2016 at 9:08 PM, Roman Vyalov >>>> wrote: >>>> >> >>>> >> +1 >>>> >> >>>> >> On Fri, Feb 26, 2016 at 12:31 PM, Aleksey Kasatkin >>>> >> wrote: >>>> >>> >>>> >>> +1 >>>> >>> >>>> >>> >>>> >>> Aleksey Kasatkin >>>> >>> >>>> >>> >>>> >>> On Thu, Feb 25, 2016 at 11:59 PM, 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 >>>> >>> >>>> >> >>>> >> >>>> >> >>>> __ >>>> >> OpenStack Development Mailing 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 >>>> >>> -- >>> Kind Regards, >>> Fedor Zhadaev >>> >>> skype: zhadaevfm >>> IRC: fzhadaev >>> >>> >>> __ >>> OpenStack Development Mailing 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 > > -- 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] Nominate Maksim Malchuk for the fuel-virtualbox-core team
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 Thu, Mar 10, 2016 at 12:40 PM, Sergey Kulanov wrote: > Voting period is over and there's no objections from cores. > So Maksim, welcome to fuel-virtualbox-core group. > > Congrats! > > 2016-03-09 13:33 GMT+02:00 Sergii Golovatiuk : > >> +1 >> >> -- >> Best regards, >> Sergii Golovatiuk, >> Skype #golserge >> IRC #holser >> >> On Wed, Mar 9, 2016 at 8:07 AM, Bulat Gaifullin >> wrote: >> >>> +1 >>> >>> Regards, >>> Bulat Gaifullin >>> Mirantis Inc. >>> >>> >>> >>> On 03 Mar 2016, at 17:03, Dmitry Klenov wrote: >>> >>> Maksim, good job! +1 from my side though I am not a core. >>> >>> On Thu, Mar 3, 2016 at 4:10 PM, Aleksey Zvyagintsev < >>> azvyagint...@mirantis.com> wrote: >>> >>>> +1 >>>> >>>> On Thu, Mar 3, 2016 at 12:57 PM, Aleksandr Didenko < >>>> adide...@mirantis.com> wrote: >>>> >>>>> +1 >>>>> >>>>> On Thu, Mar 3, 2016 at 11:00 AM, Kyrylo Galanov >>>> > wrote: >>>>> >>>>>> +1 >>>>>> >>>>>> On Thu, Mar 3, 2016 at 2:53 AM, Roman Vyalov >>>>>> wrote: >>>>>> >>>>>>> +1 >>>>>>> >>>>>>> On Wed, Mar 2, 2016 at 5:47 PM, Sergey Kulanov < >>>>>>> skula...@mirantis.com> wrote: >>>>>>> >>>>>>>> Hey Fuelers, >>>>>>>> >>>>>>>> Since we've successfully moved [1] virtual-box scripts from >>>>>>>> fuel-main [2] to >>>>>>>> separate fuel-virtualbox [3] git repo, I propose to update >>>>>>>> fuel-virtualbox-core >>>>>>>> team [4] by adding Maksim Malchuk. Maksim is the main contributor >>>>>>>> to these >>>>>>>> scripts during Mitaka release cycle [5] >>>>>>>> >>>>>>>> Fuel Cores, please vote. >>>>>>>> >>>>>>>> [1]. >>>>>>>> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086560.html >>>>>>>> [2]. https://github.com/openstack/fuel-main >>>>>>>> [3]. https://github.com/openstack/fuel-virtualbox >>>>>>>> [4]. https://review.openstack.org/#/admin/groups/1299,members >>>>>>>> [5]. https://github.com/openstack/fuel-virtualbox/commits/master >>>>>>>> >>>>>>>> -- >>>>>>>> Sergey >>>>>>>> DevOps Engineer >>>>>>>> IRC: SergK >>>>>>>> Skype: Sergey_kul >>>>>>>> >>>>>>>> >>>>>>>> __ >>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> __ >>>>>>> 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 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> __ >>>>>> OpenStack Development Mailing List (not for usage questions) >>>>>> Unsubscribe: >>>>&g
Re: [openstack-dev] [Fuel] [Openstack] Instalation Problem:VBoxManage: error: Guest not running [ubuntu14.04]
Guys, Samer has shown error messages... two lines: *VM "fuel-master" has been successfully started.* *VBoxManage: error: Guest not running* which exactly means that first command "VBoxManage startvm" has successfully executed but next one "VBoxManage " failed due to error. Which means the problem with the VM itself. Need to execute Manager (GUI), start VM manually and look at the error. On Mon, Mar 7, 2016 at 6:48 PM, Aleksey Zvyagintsev < azvyagint...@mirantis.com> wrote: > Hello, > that definitely about HDD. Create disk with at least 50Gb + > > On Mon, Mar 7, 2016 at 5:32 PM, Samer Machara < > samer.mach...@telecom-sudparis.eu> wrote: > >> Hello, >>YES, I just find the solution, the Virtualization Option on the BIOS >> was Disable by default, I turn it on and It's working now. >> Now my problem are the resources, But that's another story. JEJEJE >> >> I'm not sure if I need RAM or HD. >> >> >> >> Thanks for your help. >> >> -- >> *De: *"Igor Marnat" >> *À: *"Maksim Malchuk" >> *Cc: *"Samer Machara" , "OpenStack >> Development Mailing List (not for usage questions)" < >> openstack-dev@lists.openstack.org> >> *Envoyé: *Lundi 7 Mars 2016 11:21:42 >> >> *Objet: *Re: [openstack-dev] [Fuel] [Openstack] Instalation >> Problem:VBoxManage: error: Guest not running [ubuntu14.04] >> >> Samer, >> did you make any progress? >> >> If not yet, I have couple of questions: >> - Did you download MOS image and VBox scripts from >> https://docs.fuel-infra.org/openstack/fuel/fuel-8.0/quickstart-guide.html#downloading-the-mirantis-openstack-image >> ? >> >> - Can you login to your just deployed master node? >> >> If you can, could you please send last 50-70 strings of the file >> /var/log/puppet/bootstrap_admin_node.log from your master node? >> >> Regards, >> Igor Marnat >> >> On Fri, Mar 4, 2016 at 11:20 PM, Maksim Malchuk >> wrote: >> >>> Samer, please address my recommendations. >>> >>> >>> On Fri, Mar 4, 2016 at 7:49 PM, Samer Machara < >>> samer.mach...@telecom-sudparis.eu> wrote: >>> >>>> Hi, Igor >>>> Thanks for answer so quickly. >>>> >>>> I wait until the following message appears >>>> Installation timed out! (3000 seconds) >>>> I don't have any virtual machines created. >>>> >>>> I update to 5.0 VirtualBox version, Now I got the following message >>>> >>>> VBoxManage: error: Machine 'fuel-master' is not currently running >>>> Waiting for product VM to download files. Please do NOT abort the >>>> script... >>>> >>>> I'm still waiting >>>> >>>> -- >>>> *De: *"Maksim Malchuk" >>>> *À: *"OpenStack Development Mailing List (not for usage questions)" < >>>> openstack-dev@lists.openstack.org> >>>> *Envoyé: *Vendredi 4 Mars 2016 15:19:54 >>>> *Objet: *Re: [openstack-dev] [Fuel] [Openstack] Instalation >>>> Problem:VBoxManage: error: Guest not running [ubuntu14.04] >>>> >>>> >>>> Igor, >>>> >>>> Some information about my system: >>>> OS: ubuntu 14.04 LTS >>>> Memory: 3,8GiB >>>> >>>> Samer can't run many guests I think. >>>> >>>> >>>> On Fri, Mar 4, 2016 at 5:12 PM, Igor Marnat >>>> wrote: >>>> >>>>> Samer, Maksim, >>>>> I'd rather say that script started fuel-master already (VM >>>>> "fuel-master" has been successfully started.), didn't find running guests, >>>>> (VBoxManage: error: Guest not running) but it can try to start them >>>>> afterwards. >>>>> >>>>> Samer, >>>>> - how many VMs are there running besides fuel-master? >>>>> - is it still showing "Waiting for product VM to download files. >>>>> Please do NOT abort the script..." ? >>>>> - for how long did you wait since the message above? >>>>> >>>>> >>>>> Regards, >>>>> Igor Marnat >>>>> >>>>> On Fri, Mar 4, 2016 at 5:04 PM, Maksim Malchuk >>>>> wrote: >>>>> >>>>>>
Re: [openstack-dev] [Fuel] [Openstack] Instalation Problem:VBoxManage: error: Guest not running [ubuntu14.04]
Samer, please address my recommendations. On Fri, Mar 4, 2016 at 7:49 PM, Samer Machara < samer.mach...@telecom-sudparis.eu> wrote: > Hi, Igor > Thanks for answer so quickly. > > I wait until the following message appears > Installation timed out! (3000 seconds) > I don't have any virtual machines created. > > I update to 5.0 VirtualBox version, Now I got the following message > > VBoxManage: error: Machine 'fuel-master' is not currently running > Waiting for product VM to download files. Please do NOT abort the > script... > > I'm still waiting > > -- > *De: *"Maksim Malchuk" > *À: *"OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > *Envoyé: *Vendredi 4 Mars 2016 15:19:54 > *Objet: *Re: [openstack-dev] [Fuel] [Openstack] Instalation > Problem:VBoxManage: error: Guest not running [ubuntu14.04] > > > Igor, > > Some information about my system: > OS: ubuntu 14.04 LTS > Memory: 3,8GiB > > Samer can't run many guests I think. > > > On Fri, Mar 4, 2016 at 5:12 PM, Igor Marnat wrote: > >> Samer, Maksim, >> I'd rather say that script started fuel-master already (VM "fuel-master" >> has been successfully started.), didn't find running guests, (VBoxManage: >> error: Guest not running) but it can try to start them afterwards. >> >> Samer, >> - how many VMs are there running besides fuel-master? >> - is it still showing "Waiting for product VM to download files. Please >> do NOT abort the script..." ? >> - for how long did you wait since the message above? >> >> >> Regards, >> Igor Marnat >> >> On Fri, Mar 4, 2016 at 5:04 PM, Maksim Malchuk >> wrote: >> >>> Hi Sames, >>> >>> *VBoxManage: error: Guest not running* >>> >>> looks line the problem with VirtualBox itself or settings for the >>> 'fuel-master' VM, it can't boot it. >>> Open the VirtualBox Manger (GUI), select the 'fuel-master' VM and start >>> it manually - it should show you what is exactly happens. >>> >>> >>> On Fri, Mar 4, 2016 at 4:41 PM, Samer Machara < >>> samer.mach...@telecom-sudparis.eu> wrote: >>> >>>> Hello, everyone. >>>> I'm new with Fuel. I'm trying to follow the QuickStart Guide ( >>>> https://docs.fuel-infra.org/openstack/fuel/fuel-8.0/quickstart-guide.html), >>>> but I have the following Error: >>>> >>>> >>>> *Waiting for VM "fuel-master" to power on...* >>>> *VM "fuel-master" has been successfully started.* >>>> *VBoxManage: error: Guest not running* >>>> *VBoxManage: error: Guest not running* >>>> ... >>>> *VBoxManage: error: Guest not running* >>>> *Waiting for product VM to download files. Please do NOT abort the >>>> script...* >>>> >>>> >>>> >>>> I hope you can help me. >>>> >>>> Thanks in advance >>>> >>>> >>>> Some information about my system: >>>> OS: ubuntu 14.04 LTS >>>> Memory: 3,8GiB >>>> Processor: Intel® Core™2 Quad CPU Q9550 @ 2.83GHz × 4 >>>> OS type: 64-bit >>>> Disk 140,2GB >>>> VirtualBox Version: 4.3.36_Ubuntu >>>> Checking for 'expect'... OK >>>> Checking for 'xxd'... OK >>>> Checking for "VBoxManage"... OK >>>> Checking for VirtualBox Extension Pack... OK >>>> Checking if SSH client installed... OK >>>> Checking if ipconfig or ifconfig installed... OK >>>> >>>> >>>> I modify the config.sh to adapt my hardware configuration >>>> ... >>>> # Master node settings >>>> if [ "$CONFIG_FOR" = "4GB" ]; then >>>> vm_master_memory_mb=1024 >>>> vm_master_disk_mb=2 >>>> ... >>>> # The number of nodes for installing OpenStack on >>>> elif [ "$CONFIG_FOR" = "4GB" ]; then >>>> cluster_size=3 >>>> ... >>>> # Slave node settings. This section allows you to define CPU count for >>>> each slave node. >>>> elif [ "$CONFIG_FOR" = "4GB" ]; then >>>> vm_slave_cpu_default=1 >>>> vm_slave_cpu[1]=1 >>>> vm_slave_cpu[2]=1 >
Re: [openstack-dev] [Fuel] [Openstack] Instalation Problem:VBoxManage: error: Guest not running [ubuntu14.04]
Igor, Some information about my system: OS: ubuntu 14.04 LTS Memory: 3,8GiB Samer can't run many guests I think. On Fri, Mar 4, 2016 at 5:12 PM, Igor Marnat wrote: > Samer, Maksim, > I'd rather say that script started fuel-master already (VM "fuel-master" > has been successfully started.), didn't find running guests, (VBoxManage: > error: Guest not running) but it can try to start them afterwards. > > Samer, > - how many VMs are there running besides fuel-master? > - is it still showing "Waiting for product VM to download files. Please do > NOT abort the script..." ? > - for how long did you wait since the message above? > > > Regards, > Igor Marnat > > On Fri, Mar 4, 2016 at 5:04 PM, Maksim Malchuk > wrote: > >> Hi Sames, >> >> *VBoxManage: error: Guest not running* >> >> looks line the problem with VirtualBox itself or settings for the >> 'fuel-master' VM, it can't boot it. >> Open the VirtualBox Manger (GUI), select the 'fuel-master' VM and start >> it manually - it should show you what is exactly happens. >> >> >> On Fri, Mar 4, 2016 at 4:41 PM, Samer Machara < >> samer.mach...@telecom-sudparis.eu> wrote: >> >>> Hello, everyone. >>> I'm new with Fuel. I'm trying to follow the QuickStart Guide ( >>> https://docs.fuel-infra.org/openstack/fuel/fuel-8.0/quickstart-guide.html), >>> but I have the following Error: >>> >>> >>> *Waiting for VM "fuel-master" to power on...* >>> *VM "fuel-master" has been successfully started.* >>> *VBoxManage: error: Guest not running* >>> *VBoxManage: error: Guest not running* >>> ... >>> *VBoxManage: error: Guest not running* >>> *Waiting for product VM to download files. Please do NOT abort the >>> script...* >>> >>> >>> >>> I hope you can help me. >>> >>> Thanks in advance >>> >>> >>> Some information about my system: >>> OS: ubuntu 14.04 LTS >>> Memory: 3,8GiB >>> Processor: Intel® Core™2 Quad CPU Q9550 @ 2.83GHz × 4 >>> OS type: 64-bit >>> Disk 140,2GB >>> VirtualBox Version: 4.3.36_Ubuntu >>> Checking for 'expect'... OK >>> Checking for 'xxd'... OK >>> Checking for "VBoxManage"... OK >>> Checking for VirtualBox Extension Pack... OK >>> Checking if SSH client installed... OK >>> Checking if ipconfig or ifconfig installed... OK >>> >>> >>> I modify the config.sh to adapt my hardware configuration >>> ... >>> # Master node settings >>> if [ "$CONFIG_FOR" = "4GB" ]; then >>> vm_master_memory_mb=1024 >>> vm_master_disk_mb=2 >>> ... >>> # The number of nodes for installing OpenStack on >>> elif [ "$CONFIG_FOR" = "4GB" ]; then >>> cluster_size=3 >>> ... >>> # Slave node settings. This section allows you to define CPU count for >>> each slave node. >>> elif [ "$CONFIG_FOR" = "4GB" ]; then >>> vm_slave_cpu_default=1 >>> vm_slave_cpu[1]=1 >>> vm_slave_cpu[2]=1 >>> vm_slave_cpu[3]=1 >>> ... >>> # This section allows you to define RAM size in MB for each slave node. >>> elif [ "$CONFIG_FOR" = "4GB" ]; then >>> vm_slave_memory_default=1024 >>> >>> vm_slave_memory_mb[1]=512 >>> vm_slave_memory_mb[2]=512 >>> vm_slave_memory_mb[3]=512 >>> ... >>> # Nodes with combined roles may require more disk space. >>> if [ "$CONFIG_FOR" = "4GB" ]; then >>> vm_slave_first_disk_mb=2 >>> vm_slave_second_disk_mb=2 >>> vm_slave_third_disk_mb=2 >>> ... >>> >>> I found someone that had a similar problem ( >>> https://www.mail-archive.com/fuel-dev@lists.launchpad.net/msg01084.html), >>> he had a corrupted iso file, he solved the problem downloaded it again. I >>> downloaded the .iso file from >>> http://seed.fuel-infra.org/fuelweb-community-release/fuel-community-8.0.iso.torrent >>> . I chek the size 3,1 GB. How ever I still with the problem. >>> >>> >>> __ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >&g
Re: [openstack-dev] [Fuel] [Openstack] Instalation Problem:VBoxManage: error: Guest not running [ubuntu14.04]
Hi Sames, *VBoxManage: error: Guest not running* looks line the problem with VirtualBox itself or settings for the 'fuel-master' VM, it can't boot it. Open the VirtualBox Manger (GUI), select the 'fuel-master' VM and start it manually - it should show you what is exactly happens. On Fri, Mar 4, 2016 at 4:41 PM, Samer Machara < samer.mach...@telecom-sudparis.eu> wrote: > Hello, everyone. > I'm new with Fuel. I'm trying to follow the QuickStart Guide ( > https://docs.fuel-infra.org/openstack/fuel/fuel-8.0/quickstart-guide.html), > but I have the following Error: > > > *Waiting for VM "fuel-master" to power on...* > *VM "fuel-master" has been successfully started.* > *VBoxManage: error: Guest not running* > *VBoxManage: error: Guest not running* > ... > *VBoxManage: error: Guest not running* > *Waiting for product VM to download files. Please do NOT abort the > script...* > > > > I hope you can help me. > > Thanks in advance > > > Some information about my system: > OS: ubuntu 14.04 LTS > Memory: 3,8GiB > Processor: Intel® Core™2 Quad CPU Q9550 @ 2.83GHz × 4 > OS type: 64-bit > Disk 140,2GB > VirtualBox Version: 4.3.36_Ubuntu > Checking for 'expect'... OK > Checking for 'xxd'... OK > Checking for "VBoxManage"... OK > Checking for VirtualBox Extension Pack... OK > Checking if SSH client installed... OK > Checking if ipconfig or ifconfig installed... OK > > > I modify the config.sh to adapt my hardware configuration > ... > # Master node settings > if [ "$CONFIG_FOR" = "4GB" ]; then > vm_master_memory_mb=1024 > vm_master_disk_mb=2 > ... > # The number of nodes for installing OpenStack on > elif [ "$CONFIG_FOR" = "4GB" ]; then > cluster_size=3 > ... > # Slave node settings. This section allows you to define CPU count for > each slave node. > elif [ "$CONFIG_FOR" = "4GB" ]; then > vm_slave_cpu_default=1 > vm_slave_cpu[1]=1 > vm_slave_cpu[2]=1 > vm_slave_cpu[3]=1 > ... > # This section allows you to define RAM size in MB for each slave node. > elif [ "$CONFIG_FOR" = "4GB" ]; then > vm_slave_memory_default=1024 > > vm_slave_memory_mb[1]=512 > vm_slave_memory_mb[2]=512 > vm_slave_memory_mb[3]=512 > ... > # Nodes with combined roles may require more disk space. > if [ "$CONFIG_FOR" = "4GB" ]; then > vm_slave_first_disk_mb=2 > vm_slave_second_disk_mb=2 > vm_slave_third_disk_mb=2 > ... > > I found someone that had a similar problem ( > https://www.mail-archive.com/fuel-dev@lists.launchpad.net/msg01084.html), > he had a corrupted iso file, he solved the problem downloaded it again. I > downloaded the .iso file from > http://seed.fuel-infra.org/fuelweb-community-release/fuel-community-8.0.iso.torrent > . I chek the size 3,1 GB. How ever I still with the problem. > > __ > OpenStack Development Mailing 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] Move virtualbox scripts to a separate directory
Hi Fabrizio, The project-config patch is on the review now, waiting for a core-reviewers to merge the changes. On Wed, Feb 17, 2016 at 5:47 PM, Fabrizio Soppelsa wrote: > Vladimir, > a dedicated repo - good to hear. > Do you have a rough estimate for how long this directory will be in freeze > state? > > Thanks, > Fabrizio > > > On Feb 15, 2016, at 5:16 PM, Vladimir Kozhukalov > wrote: > > Dear colleagues, > > I'd like to announce that we are next to moving fuel-main/virtualbox > directory to a separate git repository. This directory contains a set of > bash scripts that could be used to easily deploy Fuel environment and try > to deploy OpenStack cluster using Fuel. Virtualbox is used as a > virtualization layer. > > Checklist for this change is as follows: > >1. Launchpad bug: https://bugs.launchpad.net/fuel/+bug/1544271 >2. project-config patch https://review.openstack.org/#/c/279074/2 (ON >REVIEW) >3. prepare upstream (DONE) >https://github.com/kozhukalov/fuel-virtualbox >4. .gitreview file (TODO) >5. .gitignore file (TODO) >6. MAINTAINERS file (TODO) >7. remove old files from fuel-main (TODO) > > Virtualbox directory is not actively changed, so freezing this directory > for a while is not going to affect the development process significantly. > From this moment virtualbox directory is declared freezed and all changes > in this directory that are currently in work should be later backported to > the new git repository (fuel-virtualbox). > > 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 > > -- 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] Nominate Fedor Zhadaev for the fuel-menu-core team
Congrats! On Mon, Feb 15, 2016 at 1:08 PM, Fedor Zhadaev wrote: > Thank you! > -- > Kind Regards, > Fedor Zhadaev > > skype: zhadaevfm > IRC: fzhadaev > > __ > OpenStack Development Mailing 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][Bugs] Time sync problem when testing.
I think we shouldn't depend on the other services like Syslog and logger trying to catch the problem and it is better to create the logs ourselves. On Wed, Jan 27, 2016 at 1:49 PM, Stanislaw Bogatkin wrote: > >But you've used 'logger -t ntpdate' - this is can fail again and logs can > be empty again. > What do you mean by 'fall again'? Piping to logger uses standard blocking > I/O - logger gets > all the output it can reach, so it get all output strace will produce. If > ntpdate will hang for some > reason - we should see it in strace output. If ntpdate will exit - we will > see this too. > > On Wed, Jan 27, 2016 at 12:57 PM, Maksim Malchuk > wrote: > >> But you've used 'logger -t ntpdate' - this is can fail again and logs can >> be empty again. >> My opinion we should use output redirection to the log-file directly. >> >> >> On Wed, Jan 27, 2016 at 11:21 AM, Stanislaw Bogatkin < >> sbogat...@mirantis.com> wrote: >> >>> Yes, I have created custom iso with debug output. It didn't help, so >>> another one with strace was created. >>> On Jan 27, 2016 00:56, "Alex Schultz" wrote: >>> >>>> On Tue, Jan 26, 2016 at 2:16 PM, Stanislaw Bogatkin >>>> wrote: >>>> > When there is too high strata, ntpdate can understand this and always >>>> write >>>> > this into its log. In our case there are just no log - ntpdate send >>>> first >>>> > packet, get an answer - that's all. So, fudging won't save us, as I >>>> think. >>>> > Also, it's a really bad approach to fudge a server which doesn't have >>>> a real >>>> > clock onboard. >>>> >>>> Do you have a debug output of the ntpdate somewhere? I'm not finding >>>> it in the bugs or in some of the snapshots for the failures. I did >>>> find one snapshot with the -v change that didn't have any response >>>> information so maybe it's the other problem where there is some >>>> network connectivity isn't working correctly or the responses are >>>> getting dropped somewhere? >>>> >>>> -Alex >>>> >>>> > >>>> > On Tue, Jan 26, 2016 at 10:41 PM, Alex Schultz >>> > >>>> > wrote: >>>> >> >>>> >> On Tue, Jan 26, 2016 at 11:42 AM, Stanislaw Bogatkin >>>> >> wrote: >>>> >> > Hi guys, >>>> >> > >>>> >> > for some time we have a bug [0] with ntpdate. It doesn't >>>> reproduced 100% >>>> >> > of >>>> >> > time, but breaks our BVT and swarm tests. There is no exact point >>>> where >>>> >> > problem root located. To better understand this, some verbosity to >>>> >> > ntpdate >>>> >> > output was added but in logs we can see only that packet exchange >>>> >> > between >>>> >> > ntpdate and server was started and was never completed. >>>> >> > >>>> >> >>>> >> So when I've hit this in my local environments there is usually one >>>> or >>>> >> two possible causes for this. 1) lack of network connectivity so ntp >>>> >> server never responds or 2) the stratum is too high. My assumption >>>> is >>>> >> that we're running into #2 because of our revert-resume in testing. >>>> >> When we resume, the ntp server on the master may take a while to >>>> >> become stable. This sync in the deployment uses the fuel master for >>>> >> synchronization so if the stratum is too high, it will fail with this >>>> >> lovely useless error. My assumption on what is happening is that >>>> >> because we aren't using a set of internal ntp servers but rather >>>> >> relying on the standard ntp.org pools. So when the master is being >>>> >> resumed it's struggling to find a good enough set of servers so it >>>> >> takes a while to sync. This then causes these deployment tasks to >>>> fail >>>> >> because the master has not yet stabilized (might also be geolocation >>>> >> related). We could either address this by fudging the stratum on the >>>> >> master server in the configs or possibly introducing our own more &g
Re: [openstack-dev] [Fuel][Bugs] Time sync problem when testing.
ex >> >> >> >> >> __ >> >> OpenStack Development Mailing 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 >> > > __ > OpenStack Development Mailing 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][Bugs] Time sync problem when testing.
Yes, there is no information in the logs as Stanislaw said before, also maybe exist another problem with syslog logging, so maybe on of the solution is don't use -s option or external 'logger' program, and better use simple redirection of stdout and stderr to the plain log file? On Wed, Jan 27, 2016 at 12:54 AM, Alex Schultz wrote: > Do you have a debug output of the ntpdate somewhere? I'm not finding > it in the bugs or in some of the snapshots for the failures. I did > find one snapshot with the -v change that didn't have any response > information so maybe it's the other problem where there is some > network connectivity isn't working correctly or the responses are > getting dropped somewhere? > -- 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
