Re: [openstack-dev] [magnum] Swarm Mode -- to come?

2016-10-03 Thread Fabrizio Soppelsa 
Hi Ton, I filed a high-level blueprint and assigned to you as a manager, if you 
have questions just ask.

Implementing the new Swarm as a COE should be rather straightforward, much more 
than the old Swarm. Details in the BP.

Thanks,
Fabrizio


> On Oct 3, 2016, at 9:12 AM, Ton Ngo <t...@us.ibm.com> wrote:
> 
> Hi Fabrizio,
> We had a discussion on Docker 1.12 but have not proceeded with any 
> development yet. 
> You are quite welcome to write a blueprint with details on how you envision 
> it should work. 
> This would help move the discussion along.
> Ton Ngo,
> 
> Fabrizio Soppelsa ---10/02/2016 11:26:08 AM---Hello, how about 
> the (newest) Swarm Mode (Docker 1.12+) support in Magnum?
> 
> From: Fabrizio Soppelsa <fsoppe...@mirantis.com>
> To: "OpenStack Development Mailing List (not for usage questions)" 
> <openstack-dev@lists.openstack.org>
> Date: 10/02/2016 11:26 AM
> Subject: [openstack-dev] [magnum] Swarm Mode -- to come?
> 
> 
> 
> 
> Hello,
> how about the (newest) Swarm Mode (Docker 1.12+) support in Magnum?
> I don’t find any blueprint on Launchpad on the matter yet, is this going to 
> be worked?
> 
> Ta,
> Fabrizio.
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 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>
> 
> 
> 
> __
> OpenStack Development Mailing 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,
Fabrizio Soppelsa
L2 Escalations Engineer - L2 EU team 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

[openstack-dev] [magnum] Swarm Mode -- to come?

2016-10-02 Thread Fabrizio Soppelsa 
Hello,
how about the (newest) Swarm Mode (Docker 1.12+) support in Magnum?
I don’t find any blueprint on Launchpad on the matter yet, is this going to be 
worked?

Ta,
Fabrizio.
__
OpenStack Development Mailing 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

2016-02-17 Thread Fabrizio Soppelsa 
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:
> Launchpad bug: https://bugs.launchpad.net/fuel/+bug/1544271 
> 
> project-config patch https://review.openstack.org/#/c/279074/2 
>  (ON REVIEW)
> prepare upstream (DONE) https://github.com/kozhukalov/fuel-virtualbox 
> 
> .gitreview file (TODO)
> .gitignore file (TODO)
> MAINTAINERS file (TODO)
> 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

Re: [openstack-dev] neutron metadata-agent HA

2015-12-11 Thread Fabrizio Soppelsa 

> On Dec 10, 2015, at 12:56 AM, Alvise Dorigo  wrote:
> 
> So my question is: is there any progress on this topic ? is there a way 
> (something like a cronjob script) to make the metadata-agent redundant 
> without involving the clustering software Pacemaker/Corosync ?

Reason for such a dirty solution instead of rely onto pacemaker?

I’m not aware of such initiatives - just checked the blueprints in Neutron and 
I found no relevant. I can suggest to file a proposal to the correspondent 
launchpad page, by elaborating your idea.

F.__
OpenStack Development Mailing 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] Get rid of fuelmenu

2015-07-23 Thread Fabrizio Soppelsa 

Hello Vladimir, from me -1.

We can discuss if enable fuelmenu=yes or not in grub, but I wouldn't get 
rid of it. I've never heard complaints against fuelmenu from users, and 
it's widely used for basic settings afterinstall.


If the users had to manually edit another configuration file, should 
they remember to run a validator tool over it every time after editing 
the file? Or do we add a futher layer that invokes $EDITOR and after 
:wq, some validator performs a check...? IMO that's poor UX, and why 
reimplement it, in fuelmenu there are already nice fixed choices and 
check commands that restricts potential human mistakes.


F.


On 07/23/2015 04:23 AM, Vladimir Kozhukalov wrote:

Dear colleagues,

What do you think of getting rid of fuelmenu and substituting it with 
thoroughly commented text file + some validation + vim? The major pro 
of this is that text file is easier to extend and edit. Many people 
prefer vim UX instead of wandering through the semi-graphical 
interface. And it is not so hard to implement syntax and logic 
checking for the text file.


Please give your opinions about this.

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] Developers in the Bay Area

2015-06-17 Thread Fabrizio Soppelsa 

Lisette, what is this about?
http://it.linkedin.com/in/fsoppelsa


On 06/17/2015 07:10 AM, Lisette Sheehan wrote:


Hi!

I work for an events market research company and am in need of 
recruiting young developers in the San Francisco Bay Area to answer a 
short survey to see if they qualify for an in-depth interview 
regarding an upcoming developer event in San Francisco. Is this 
something I can post your page or send out to your mailing list?


*Lisette*

*Lisette Sheehan, *Senior Research Manager

*Exhibit Surveys**, Inc.*

7 Hendrickson Ave., Red Bank, NJ 07701

T: 732.704.1329   |  Mobile: 732.598.9313   |  F: 732.741.5704

E: _lise...@exhibitsurveys.com mailto:lise...@exhibitsurveys.com_

*Be a Knowbody*: www.exhibitsurveys.com

*Follow us on *Facebook 
http://www.facebook.com/pages/Exhibit-Surveys-Inc/77619067606*and 
*Twitter http://twitter.com/exhibitsurveys




__
OpenStack Development Mailing 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 Irina Povolotskaya for fuel-docs core

2015-03-26 Thread Fabrizio Soppelsa 

+1 definitely


On 03/25/2015 10:10 PM, Dmitry Borodaenko wrote:

Fuelers,

I'd like to nominate Irina Povolotskaya for the fuel-docs-core team.
She has contributed thousands of lines of documentation to Fuel over
the past several months, and has been a diligent reviewer:

http://stackalytics.com/?user_id=ipovolotskayarelease=allproject_type=allmodule=fuel-docs

I believe it's time to grant her core reviewer rights in the fuel-docs
repository.

Core reviewer approval process definition:
https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess




__
OpenStack Development Mailing 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 master monitoring

2015-01-27 Thread Fabrizio Soppelsa 
The proposed monitoring options make sense, since the Fuel master has nothing 
yet, but I would like to ressurect this thread to see if we can discuss some 
strategies in order to avoid the /var/log fillup with consequent docker 
containers corruption.

Now, a customer facing this corruption can recover the master, as described in 
our documentation [1].
Of course, if we could avoid the problem at all, it would be even better. So, 
do we have a strategy in progress on this?

As a first attempt, I filed a blueprint, proposing to separate /var/log [2]. 

Thanks,
Fabrizio.


[1] 
http://docs.mirantis.com/openstack/fuel/fuel-5.1/operations.html#fuel-master-and-docker-disk-space-troubleshooting
 
http://docs.mirantis.com/openstack/fuel/fuel-5.1/operations.html#fuel-master-and-docker-disk-space-troubleshooting
[2] https://blueprints.launchpad.net/fuel/+spec/isolate-var-log-on-master 
https://blueprints.launchpad.net/fuel/+spec/isolate-var-log-on-master 


 On 21 Nov 2014, at 12:01, Matthew Mosesohn mmoses...@mirantis.com wrote:
 
 I'm okay with Sensu or Monit, just as long as the results of
 monitoring can be represented in a web UI and has a configurable
 option for email alerting. Tight integration with Fuel Web is a
 nice-to-have (via AMQP perhaps), but anything that can solve our
 out-of-disk scenario is ideal. I did my best to tune our logging and
 logs rotation, but monitoring is the most sensible approach.
 
 -Matthew
 
 On Fri, Nov 21, 2014 at 12:21 PM, Przemyslaw Kaminski
 pkamin...@mirantis.com wrote:
 BTW, there's also Monit
 
 http://mmonit.com/monit/
 
 (though it's in C) that looks quite nice. Some config examples:
 
 http://omgitsmgp.com/2013/09/07/a-monit-primer/
 
 P.
 
 On 11/20/2014 09:13 PM, Dmitriy Shulyak wrote:
 
 Guys, maybe we can use existing software, for example Sensu [1]?
 Maybe i am wrong, but i dont like the idea to start writing our small
 monitoring applications..
 Also something well designed and extendable can be reused for statistic
 collector
 
 
 1. https://github.com/sensu
 
 On Wed, Nov 12, 2014 at 12:47 PM, Tomasz Napierala tnapier...@mirantis.com
 wrote:
 
 
 On 06 Nov 2014, at 12:20, Przemyslaw Kaminski pkamin...@mirantis.com
 wrote:
 
 I didn't mean a robust monitoring system, just something simpler.
 Notifications is a good idea for FuelWeb.
 
 I’m all for that, but if we add it, we need to document ways to clean up
 space.
 We could also add some kind of simple job to remove rotated logs, obsolete
 spanshots, etc., but this is out of scope for 6.0 I guess.
 
 Regards,
 --
 Tomasz 'Zen' Napierala
 Sr. OpenStack Engineer
 tnapier...@mirantis.com
 
 
 
 
 
 
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
 
 
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
 
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 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