Re: Miami CCC '17 Roundtable/Hackathon Summary

[Ron Wheeler]

+1
To find out if it is too complex to be worth doing, try writing the docs 
for it and see if system managers can actually read it and tell you how 
it works and what it is good for.
If they can not, you can save a lot of coding and make adoption more 
likely by not doing it.


On 23/05/2017 11:29 PM, Marty Godsey wrote:

Thank you Simon for the re-cap of the hackathon. I was able to catch the last 
couple of hours of it but saw the notes on the boards..

I am going to give my thoughts on this coming from a slightly different angle. As many of 
you know, I am not a coder. I am an Systems/Network Engineer. I know many times design 
decisions are made based upon the amount of time it will require to write a particular 
piece of code, update, fix bugs, etc. But the one thing we can't forget is that many ACS 
users may not have the ability to add their own plugins, write code to interact with a 
router, etc. I know I can't myself, going back to the I'm not a coder, but thankfully I 
know people that can and can get it done if need be but the point is many people cannot. 
As we decide how we are going to re-write the networking portions of ACS we have to step 
back and take a look at what was one of the most talked about topics at this year's CCC. 
I am not talking about the networking, IPV6 support or any other cool idea we had. The 
constant conversation in the hallways and at the many "Zest" outings was 
ADOPTION and MARKET AWARENESS.

Adoption.. How do we get the word out and get it adopted by more people? It’s a tough question but 
something that also has to influence how we build ACS. Let take a moment and compare ACS to its 
closest competitor Openstack. We all know that Openstack has the market share, it has the money 
behind it. But what is the constant complaint we hear from people who use? ""Yea, it 
works but man,, it was a bi%#h to get going""  Openstack has gotten its adoption cause it 
had big names and a lot of money behind it. Openstacks complexity has also caused it to not be 
adopted in many cases. Your typical IT shop in a small to medium sized business does not have the 
expertise to implement something like this. And when I say SMB I am saying organizations from 
10-500 people.

So back to my adoption question. As mentioned before one of the reasons many 
people come to ACS is the fact that it has it all. Networking, hyper-visor 
management, user management, storage management, its multi-tenant. What will 
drive ACS adoption will be improving what ACS already does, not making it more 
like OpenStack. Now do I think that having a module service or plugin service 
to provide a framework to allow for external resources to be used by ACS is a 
good thing? Yes I do. But I also do not want to, and hope we don’t, move away 
from what made ACS what it is today. A software that allows companies to easily 
spin up new public or private clouds. Adoption-Centric Usability.

If I rambled a little here I apologize, its 11:30pm and sometimes I get ahead 
of myself (especially when I write something like this at this hour) when 
writing about something I am passionate about and I am passionate about getting 
more exposure and adoption of ACS.

Thank you for listening guys.. Sorry for the ramble.

Regards,
Marty Godsey
Principal Engineer
nSource Solutions, LLC

-Original Message-
From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com]
Sent: Tuesday, May 23, 2017 11:18 AM
To: dev@cloudstack.apache.org
Subject: Re: Miami CCC '17 Roundtable/Hackathon Summary

I missed the roundtable and hackathon, my bad guys :(

I liked the ideas that you (all) put forward. The VR is interesting and a nice 
feature to have, but it causes some pain to maintain in our development cycles. 
The idea to split the current VR into NFV is great; this can make things more 
pluggable and take ACS to NFV (officially). We could develop a framework in ACS 
(an API method?) that creates a system VM called NFV where people (vendors, 
enthusiast, users and others) can then extend and add their functions/systems 
there. The problem is the work required to design and develop such thing.

I use Daan`s words here, this is a community effort and not a single company or 
individual. What do you guys think? We could start creating a roadmap of when 
we want this feature (milestones for delivering piece by piece of the complete 
feature), then the draft of a proposal, and later define the implementation 
job, so people of the community can embrace it.

On Tue, May 23, 2017 at 10:18 AM, Daan Hoogland  wrote:

 Hi everyone,


 During the CCC 

Re: GSoC'17

[sachin patil]

Hello,

Attaching two pics for reference.

sucessfully installed mysql connector but installation is not recognized




On Wed, May 24, 2017 at 9:44 AM, Syed Ahmed  wrote:

> Hey Sachin,
>
> Were you able to get everything setup?
>
> Thanks,
> -Syed
>
> On Tue, May 23, 2017 at 5:19 AM, Rohit Yadav 
> wrote:
>
>> Sachin,
>>
>> To install mysql.connector, try this:
>>
>> sudo pip install --upgrade http://cdn.mysql.com/Downloads
>> /Connector-Python/mysql-connector-python-2.0.4.zip#
>> md5=3df394d89300db95163f17c843ef49df
>>
>> Now, retry build+package etc.
>>
>> Regards.
>>
>> rohit.ya...@shapeblue.com
>> www.shapeblue.com
>> @shapeblue
>>
>>
>>
>> --
>> *From:* sachin patil 
>> *Sent:* 23 May 2017 14:09:53
>> *To:* Rohit Yadav
>> *Cc:* dev; Syed Ahmed
>> *Subject:* Re: GSoC'17
>>
>> Hello rohit,
>>
>>
>> Yesterday I tried to install all dependencies . I have installed all
>> dependencies you mentioned expect Python - MySQL.connector. I have
>> installed it using  sudo apt-get python-mysql.connector it installs
>> successfully . But if I try to package it after using ./build-deb.sh it
>> still says Python MySQL connector dependency unmet
>>
>> I am trying to solve this right now
>>
>> On 23-May-2017 1:57 PM, "Rohit Yadav"  wrote:
>>
>>> Sachin,
>>>
>>>
>>> I think you're trying to build deb packages. To do this on your
>>> Ubuntu16.04 based environment, install the build dependencies as defined in
>>> the *debian/control* file (apt-get install them)
>>>
>>>
>>> *Build-Depends: debhelper (>= 9), openjdk-8-jdk | java8-sdk | java8-jdk
>>> | openjdk-7-jdk, genisoimage,*
>>> * python-mysql.connector, maven (>= 3) | maven3, python (>= 2.7),
>>> lsb-release, dh-systemd*
>>>
>>> You may also consider to use a docker container image I had created for
>>> this purpose, we use this container in all of the blueorangutan-trillian CI
>>> tests:
>>>
>>> https://hub.docker.com/r/bhaisaab/ubuntu-cloudstack-slave/
>>>
>>> Reference deb-pkg build script using above docker container:
>>> https://gist.github.com/rhtyd/57c5b904c1f25455126cbc6b1c0bb83f
>>>
>>>
>>> Regards.
>>> --
>>> *From:* sachin patil 
>>> *Sent:* 22 May 2017 23:50:13
>>> *To:* Syed Ahmed
>>> *Cc:* dev
>>> *Subject:* Re: GSoC'17
>>>
>>> Hello,
>>>
>>> Sry to be late. The output of the first command mvn install -P deps
>>> https://drive.google.com/file/d/0B250zd28Pn8WWklXdVdHZGdyVzg
>>> /view?usp=sharing
>>>
>>> output of second command dpkg-buildpackage
>>>
>>> dpkg-buildpackage: source package cloudstack
>>> dpkg-buildpackage: source version 4.10.0.0-SNAPSHOT
>>> dpkg-buildpackage: source distribution unstable
>>> dpkg-buildpackage: source changed by the Apache CloudStack project <
>>> dev@cloudstack.apache.org>
>>> dpkg-buildpackage: host architecture amd64
>>> dpkg-source --before-build cloudstack
>>> dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 9)
>>> python-mysql.connector dh-systemd
>>> dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
>>> aborting
>>> dpkg-buildpackage: warning: (Use -d flag to override.)
>>>
>>> On Mon, May 22, 2017 at 11:47 PM, sachin patil 
>>> wrote:
>>>
>>> > Hello,
>>> >
>>> > Sry to be late. The output of the first command mvn install -P deps
>>> > attached in the mail.
>>> >
>>> > output of second command dpkg-buildpackage
>>> >
>>> > dpkg-buildpackage: source package cloudstack
>>> > dpkg-buildpackage: source version 4.10.0.0-SNAPSHOT
>>> > dpkg-buildpackage: source distribution unstable
>>> > dpkg-buildpackage: source changed by the Apache CloudStack project <
>>> > dev@cloudstack.apache.org>
>>> > dpkg-buildpackage: host architecture amd64
>>> > dpkg-source --before-build cloudstack
>>> > dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 9)
>>> > python-mysql.connector dh-systemd
>>> > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
>>> > aborting
>>> > dpkg-buildpackage: warning: (Use -d flag to override.)
>>> >
>>> >
>>> > On Mon, May 22, 2017 at 9:59 PM, sachin patil 
>>> > wrote:
>>> >
>>> >> I am stuck in rain.
>>> >> thanks for the info sir. will do all relevant checks and mail you in
>>> an
>>> >> hour
>>> >>
>>> >> On 22-May-2017 9:55 PM, "Syed Ahmed"  wrote:
>>> >>
>>> >>> FYI, if you find the problem even with latest 4.9 agent. Try building
>>> >>> the debs and install them on the host
>>> >>>
>>> >>> mvn install -P deps && dpkg-buildpackage
>>> >>>
>>> >>>
>>> >>>
>>> >>> On Mon, May 22, 2017 at 10:43 AM, Daan Hoogland <
>>> daan.hoogl...@gmail.com
>>> >>> > wrote:
>>> >>>
>>>  On Mon, May 22, 2017 at 4:37 PM, sachin patil <
>>> sachin931...@gmail.com>
>>>  wrote:
>>>  >
>>>  >> > >> According to the link you told me to enter in acs.list
>>> in
>>>  source.d
>>>  >> > >> 

Re: GSoC'17

[Syed Ahmed]

Hey Sachin,

Were you able to get everything setup?

Thanks,
-Syed

On Tue, May 23, 2017 at 5:19 AM, Rohit Yadav 
wrote:

> Sachin,
>
> To install mysql.connector, try this:
>
> sudo pip install --upgrade http://cdn.mysql.com/
> Downloads/Connector-Python/mysql-connector-python-2.0.4.zip#md5=
> 3df394d89300db95163f17c843ef49df
>
> Now, retry build+package etc.
>
> Regards.
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
>
>
> --
> *From:* sachin patil 
> *Sent:* 23 May 2017 14:09:53
> *To:* Rohit Yadav
> *Cc:* dev; Syed Ahmed
> *Subject:* Re: GSoC'17
>
> Hello rohit,
>
>
> Yesterday I tried to install all dependencies . I have installed all
> dependencies you mentioned expect Python - MySQL.connector. I have
> installed it using  sudo apt-get python-mysql.connector it installs
> successfully . But if I try to package it after using ./build-deb.sh it
> still says Python MySQL connector dependency unmet
>
> I am trying to solve this right now
>
> On 23-May-2017 1:57 PM, "Rohit Yadav"  wrote:
>
>> Sachin,
>>
>>
>> I think you're trying to build deb packages. To do this on your
>> Ubuntu16.04 based environment, install the build dependencies as defined in
>> the *debian/control* file (apt-get install them)
>>
>>
>> *Build-Depends: debhelper (>= 9), openjdk-8-jdk | java8-sdk | java8-jdk |
>> openjdk-7-jdk, genisoimage,*
>> * python-mysql.connector, maven (>= 3) | maven3, python (>= 2.7),
>> lsb-release, dh-systemd*
>>
>> You may also consider to use a docker container image I had created for
>> this purpose, we use this container in all of the blueorangutan-trillian CI
>> tests:
>>
>> https://hub.docker.com/r/bhaisaab/ubuntu-cloudstack-slave/
>>
>> Reference deb-pkg build script using above docker container:
>> https://gist.github.com/rhtyd/57c5b904c1f25455126cbc6b1c0bb83f
>>
>>
>> Regards.
>> --
>> *From:* sachin patil 
>> *Sent:* 22 May 2017 23:50:13
>> *To:* Syed Ahmed
>> *Cc:* dev
>> *Subject:* Re: GSoC'17
>>
>> Hello,
>>
>> Sry to be late. The output of the first command mvn install -P deps
>> https://drive.google.com/file/d/0B250zd28Pn8WWklXdVdHZGdyVzg
>> /view?usp=sharing
>>
>> output of second command dpkg-buildpackage
>>
>> dpkg-buildpackage: source package cloudstack
>> dpkg-buildpackage: source version 4.10.0.0-SNAPSHOT
>> dpkg-buildpackage: source distribution unstable
>> dpkg-buildpackage: source changed by the Apache CloudStack project <
>> dev@cloudstack.apache.org>
>> dpkg-buildpackage: host architecture amd64
>> dpkg-source --before-build cloudstack
>> dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 9)
>> python-mysql.connector dh-systemd
>> dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
>> aborting
>> dpkg-buildpackage: warning: (Use -d flag to override.)
>>
>> On Mon, May 22, 2017 at 11:47 PM, sachin patil 
>> wrote:
>>
>> > Hello,
>> >
>> > Sry to be late. The output of the first command mvn install -P deps
>> > attached in the mail.
>> >
>> > output of second command dpkg-buildpackage
>> >
>> > dpkg-buildpackage: source package cloudstack
>> > dpkg-buildpackage: source version 4.10.0.0-SNAPSHOT
>> > dpkg-buildpackage: source distribution unstable
>> > dpkg-buildpackage: source changed by the Apache CloudStack project <
>> > dev@cloudstack.apache.org>
>> > dpkg-buildpackage: host architecture amd64
>> > dpkg-source --before-build cloudstack
>> > dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 9)
>> > python-mysql.connector dh-systemd
>> > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
>> > aborting
>> > dpkg-buildpackage: warning: (Use -d flag to override.)
>> >
>> >
>> > On Mon, May 22, 2017 at 9:59 PM, sachin patil 
>> > wrote:
>> >
>> >> I am stuck in rain.
>> >> thanks for the info sir. will do all relevant checks and mail you in an
>> >> hour
>> >>
>> >> On 22-May-2017 9:55 PM, "Syed Ahmed"  wrote:
>> >>
>> >>> FYI, if you find the problem even with latest 4.9 agent. Try building
>> >>> the debs and install them on the host
>> >>>
>> >>> mvn install -P deps && dpkg-buildpackage
>> >>>
>> >>>
>> >>>
>> >>> On Mon, May 22, 2017 at 10:43 AM, Daan Hoogland <
>> daan.hoogl...@gmail.com
>> >>> > wrote:
>> >>>
>>  On Mon, May 22, 2017 at 4:37 PM, sachin patil <
>> sachin931...@gmail.com>
>>  wrote:
>>  >
>>  >> > >> According to the link you told me to enter in acs.list in
>>  source.d
>>  >> > >> folder. Cloudstack-agent 4.9.2 is installed.  I build CS
>>  management
>>  >> from
>>  >> > >> code 4.10.0.0 snapshot.
>> 
>> 
>>  You better have a look at this. Does the agent and the ms both
>> support
>>  (the same version of) that setup host params command? something might
>>  have changed between 4.9.2 and 4.10 snapshot.
>> 

RE: Miami CCC '17 Roundtable/Hackathon Summary

[Marty Godsey]

Thank you Simon for the re-cap of the hackathon. I was able to catch the last 
couple of hours of it but saw the notes on the boards..

I am going to give my thoughts on this coming from a slightly different angle. 
As many of you know, I am not a coder. I am an Systems/Network Engineer. I know 
many times design decisions are made based upon the amount of time it will 
require to write a particular piece of code, update, fix bugs, etc. But the one 
thing we can't forget is that many ACS users may not have the ability to add 
their own plugins, write code to interact with a router, etc. I know I can't 
myself, going back to the I'm not a coder, but thankfully I know people that 
can and can get it done if need be but the point is many people cannot. As we 
decide how we are going to re-write the networking portions of ACS we have to 
step back and take a look at what was one of the most talked about topics at 
this year's CCC. I am not talking about the networking, IPV6 support or any 
other cool idea we had. The constant conversation in the hallways and at the 
many "Zest" outings was ADOPTION and MARKET AWARENESS.

Adoption.. How do we get the word out and get it adopted by more people? It’s a 
tough question but something that also has to influence how we build ACS. Let 
take a moment and compare ACS to its closest competitor Openstack. We all know 
that Openstack has the market share, it has the money behind it. But what is 
the constant complaint we hear from people who use? ""Yea, it works but man,, 
it was a bi%#h to get going""  Openstack has gotten its adoption cause it had 
big names and a lot of money behind it. Openstacks complexity has also caused 
it to not be adopted in many cases. Your typical IT shop in a small to medium 
sized business does not have the expertise to implement something like this. 
And when I say SMB I am saying organizations from 10-500 people.

So back to my adoption question. As mentioned before one of the reasons many 
people come to ACS is the fact that it has it all. Networking, hyper-visor 
management, user management, storage management, its multi-tenant. What will 
drive ACS adoption will be improving what ACS already does, not making it more 
like OpenStack. Now do I think that having a module service or plugin service 
to provide a framework to allow for external resources to be used by ACS is a 
good thing? Yes I do. But I also do not want to, and hope we don’t, move away 
from what made ACS what it is today. A software that allows companies to easily 
spin up new public or private clouds. Adoption-Centric Usability. 

If I rambled a little here I apologize, its 11:30pm and sometimes I get ahead 
of myself (especially when I write something like this at this hour) when 
writing about something I am passionate about and I am passionate about getting 
more exposure and adoption of ACS.

Thank you for listening guys.. Sorry for the ramble.

Regards,
Marty Godsey
Principal Engineer
nSource Solutions, LLC

-Original Message-
From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com] 
Sent: Tuesday, May 23, 2017 11:18 AM
To: dev@cloudstack.apache.org
Subject: Re: Miami CCC '17 Roundtable/Hackathon Summary

I missed the roundtable and hackathon, my bad guys :(

I liked the ideas that you (all) put forward. The VR is interesting and a nice 
feature to have, but it causes some pain to maintain in our development cycles. 
The idea to split the current VR into NFV is great; this can make things more 
pluggable and take ACS to NFV (officially). We could develop a framework in ACS 
(an API method?) that creates a system VM called NFV where people (vendors, 
enthusiast, users and others) can then extend and add their functions/systems 
there. The problem is the work required to design and develop such thing.

I use Daan`s words here, this is a community effort and not a single company or 
individual. What do you guys think? We could start creating a roadmap of when 
we want this feature (milestones for delivering piece by piece of the complete 
feature), then the draft of a proposal, and later define the implementation 
job, so people of the community can embrace it.

On Tue, May 23, 2017 at 10:18 AM, Daan Hoogland  wrote:

> Great thanks Simon,
>
> Just want to play bingo a bit; dividing the VR into VNFs (virtual 
> network
> functions) was mentioned. This pertains to the mention of making the 
> VR more modular ;)
>
> Hopefully everybody is inspired by this because no one company or 
> person is going to make this happen.
>
> Dahn
>
> On 23/05/17 14:16, "Simon Weller"  wrote:
>
> Hi everyone,
>
>
> During the CCC last week in Miami, we held a roundtable/hackathon 
> to discuss some of the major areas the community would like to focus 
> more attention.
>
>
> The discussions were passionate and were mainly focused around 
> networking and our current use of our home-spun Virtual Router.
>
>
> 

Re: Miami CCC '17 Roundtable/Hackathon Summary

[Rafael Weingärtner]

I missed the roundtable and hackathon, my bad guys :(

I liked the ideas that you (all) put forward. The VR is interesting and a
nice feature to have, but it causes some pain to maintain in our
development cycles. The idea to split the current VR into NFV is great;
this can make things more pluggable and take ACS to NFV (officially). We
could develop a framework in ACS (an API method?) that creates a system VM
called NFV where people (vendors, enthusiast, users and others) can then
extend and add their functions/systems there. The problem is the work
required to design and develop such thing.

I use Daan`s words here, this is a community effort and not a single
company or individual. What do you guys think? We could start creating a
roadmap of when we want this feature (milestones for delivering piece by
piece of the complete feature), then the draft of a proposal, and later
define the implementation job, so people of the community can embrace it.

On Tue, May 23, 2017 at 10:18 AM, Daan Hoogland  wrote:

> Great thanks Simon,
>
> Just want to play bingo a bit; dividing the VR into VNFs (virtual network
> functions) was mentioned. This pertains to the mention of making the VR
> more modular ;)
>
> Hopefully everybody is inspired by this because no one company or person
> is going to make this happen.
>
> Dahn
>
> On 23/05/17 14:16, "Simon Weller"  wrote:
>
> Hi everyone,
>
>
> During the CCC last week in Miami, we held a roundtable/hackathon to
> discuss some of the major areas the community would like to focus more
> attention.
>
>
> The discussions were passionate and were mainly focused around
> networking and our current use of our home-spun Virtual Router.
>
>
> For most of the us, the VR has become a challenging beast, mainly due
> to how difficult it is to end-to-end test for new releases.
>
> Quite often PRs are pushed that fix an issue on one feature set, but
> break another unintentionally. This has a great deal to do with how
> inter-mingled all the features are currently.
>
>
> We floated some ideas related to short term VR fixes in order to make
> it more modular, as well as API driven, rather than the currently SSH JSON
> injections.
>
> A number of possible alternatives were also brought up to see what VR
> feature coverage could be handled by other virtual appliances currently out
> on the market.
>
>
> These included (but not limited to):
>
>
> VyOS (current PR out there for integration via a plugin – thanks
> Matthew!)
>
> Microtek (Commerical)
>
> Openswitch/Flexswitch
>
> Cloud Router
>
>
> The second major topic of the day was related to how we want to
> integrate networking moving forward.
>
>
> A fair number of individuals felt that we shouldn't be focusing so
> much on integrating network functions, but relying on other network
> orchestrators to hand this.
>
> It was also noted that what draws a lot of people to ACS is the fact
> we have a VR and do provide these functions out of the box.
>
>
> We discussed how we could standardize the network sub system to use
> some sort of queuing bus to make it easier for others projects to integrate
> their solutions.
>
> The current plugin implementation is fairly complex and often other
> projects (or commercial entities) put it into the too hard basket, until
> someone either does it themselves or is willing to pay for the development.
>
> Most also felt it was important to maintain a default network function
> that works out of the box so that the complexity of a full orchestrator
> could be avoided if not needed.
>
>
> I'm sure I've missed some key points, so hopefully this starts a
> discussion with the entire community of where we focused next.
>
>
> Thanks to all those that participated on Tuesday afternoon.
>
>
> - Si
>
>
>
>
> daan.hoogl...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>


-- 
Rafael Weingärtner

Re: Miami CCC '17 Roundtable/Hackathon Summary

[Daan Hoogland]

Great thanks Simon,

Just want to play bingo a bit; dividing the VR into VNFs (virtual network 
functions) was mentioned. This pertains to the mention of making the VR more 
modular ;)

Hopefully everybody is inspired by this because no one company or person is 
going to make this happen.

Dahn

On 23/05/17 14:16, "Simon Weller"  wrote:

Hi everyone,


During the CCC last week in Miami, we held a roundtable/hackathon to 
discuss some of the major areas the community would like to focus more 
attention.


The discussions were passionate and were mainly focused around networking 
and our current use of our home-spun Virtual Router.


For most of the us, the VR has become a challenging beast, mainly due to 
how difficult it is to end-to-end test for new releases.

Quite often PRs are pushed that fix an issue on one feature set, but break 
another unintentionally. This has a great deal to do with how inter-mingled all 
the features are currently.


We floated some ideas related to short term VR fixes in order to make it 
more modular, as well as API driven, rather than the currently SSH JSON 
injections.

A number of possible alternatives were also brought up to see what VR 
feature coverage could be handled by other virtual appliances currently out on 
the market.


These included (but not limited to):


VyOS (current PR out there for integration via a plugin – thanks Matthew!)

Microtek (Commerical)

Openswitch/Flexswitch

Cloud Router


The second major topic of the day was related to how we want to integrate 
networking moving forward.


A fair number of individuals felt that we shouldn't be focusing so much on 
integrating network functions, but relying on other network orchestrators to 
hand this.

It was also noted that what draws a lot of people to ACS is the fact we 
have a VR and do provide these functions out of the box.


We discussed how we could standardize the network sub system to use some 
sort of queuing bus to make it easier for others projects to integrate their 
solutions.

The current plugin implementation is fairly complex and often other 
projects (or commercial entities) put it into the too hard basket, until 
someone either does it themselves or is willing to pay for the development.

Most also felt it was important to maintain a default network function that 
works out of the box so that the complexity of a full orchestrator could be 
avoided if not needed.


I'm sure I've missed some key points, so hopefully this starts a discussion 
with the entire community of where we focused next.


Thanks to all those that participated on Tuesday afternoon.


- Si




daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Miami CCC '17 Roundtable/Hackathon Summary

[Simon Weller]

Hi everyone,


During the CCC last week in Miami, we held a roundtable/hackathon to discuss 
some of the major areas the community would like to focus more attention.


The discussions were passionate and were mainly focused around networking and 
our current use of our home-spun Virtual Router.


For most of the us, the VR has become a challenging beast, mainly due to how 
difficult it is to end-to-end test for new releases.

Quite often PRs are pushed that fix an issue on one feature set, but break 
another unintentionally. This has a great deal to do with how inter-mingled all 
the features are currently.


We floated some ideas related to short term VR fixes in order to make it more 
modular, as well as API driven, rather than the currently SSH JSON injections.

A number of possible alternatives were also brought up to see what VR feature 
coverage could be handled by other virtual appliances currently out on the 
market.


These included (but not limited to):


VyOS (current PR out there for integration via a plugin – thanks Matthew!)

Microtek (Commerical)

Openswitch/Flexswitch

Cloud Router


The second major topic of the day was related to how we want to integrate 
networking moving forward.


A fair number of individuals felt that we shouldn't be focusing so much on 
integrating network functions, but relying on other network orchestrators to 
hand this.

It was also noted that what draws a lot of people to ACS is the fact we have a 
VR and do provide these functions out of the box.


We discussed how we could standardize the network sub system to use some sort 
of queuing bus to make it easier for others projects to integrate their 
solutions.

The current plugin implementation is fairly complex and often other projects 
(or commercial entities) put it into the too hard basket, until someone either 
does it themselves or is willing to pay for the development.

Most also felt it was important to maintain a default network function that 
works out of the box so that the complexity of a full orchestrator could be 
avoided if not needed.


I'm sure I've missed some key points, so hopefully this starts a discussion 
with the entire community of where we focused next.


Thanks to all those that participated on Tuesday afternoon.


- Si

Re: GSoC'17

[Rohit Yadav]

Sachin,

To install mysql.connector, try this:

sudo pip install --upgrade 
http://cdn.mysql.com/Downloads/Connector-Python/mysql-connector-python-2.0.4.zip#md5=3df394d89300db95163f17c843ef49df

Now, retry build+package etc.

Regards.

From: sachin patil 
Sent: 23 May 2017 14:09:53
To: Rohit Yadav
Cc: dev; Syed Ahmed
Subject: Re: GSoC'17

Hello rohit,


Yesterday I tried to install all dependencies . I have installed all 
dependencies you mentioned expect Python - MySQL.connector. I have installed it 
using  sudo apt-get python-mysql.connector it installs successfully . But if I 
try to package it after using ./build-deb.sh it still says Python MySQL 
connector dependency unmet

I am trying to solve this right now

On 23-May-2017 1:57 PM, "Rohit Yadav" 
> wrote:

Sachin,


I think you're trying to build deb packages. To do this on your Ubuntu16.04 
based environment, install the build dependencies as defined in the 
debian/control file (apt-get install them)

Build-Depends: debhelper (>= 9), openjdk-8-jdk | java8-sdk | java8-jdk | 
openjdk-7-jdk, genisoimage,
 python-mysql.connector, maven (>= 3) | maven3, python (>= 2.7), lsb-release, 
dh-systemd


You may also consider to use a docker container image I had created for this 
purpose, we use this container in all of the blueorangutan-trillian CI tests:

https://hub.docker.com/r/bhaisaab/ubuntu-cloudstack-slave/


Reference deb-pkg build script using above docker container: 
https://gist.github.com/rhtyd/57c5b904c1f25455126cbc6b1c0bb83f


Regards.


From: sachin patil >
Sent: 22 May 2017 23:50:13
To: Syed Ahmed
Cc: dev
Subject: Re: GSoC'17

Hello,

Sry to be late. The output of the first command mvn install -P deps
https://drive.google.com/file/d/0B250zd28Pn8WWklXdVdHZGdyVzg/view?usp=sharing

output of second command dpkg-buildpackage

dpkg-buildpackage: source package cloudstack
dpkg-buildpackage: source version 4.10.0.0-SNAPSHOT
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by the Apache CloudStack project <
dev@cloudstack.apache.org>
dpkg-buildpackage: host architecture amd64
dpkg-source --before-build cloudstack
dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 9)
python-mysql.connector dh-systemd
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
aborting
dpkg-buildpackage: warning: (Use -d flag to override.)

On Mon, May 22, 2017 at 11:47 PM, sachin patil 
>
wrote:

> Hello,
>
> Sry to be late. The output of the first command mvn install -P deps
> attached in the mail.
>
> output of second command dpkg-buildpackage
>
> dpkg-buildpackage: source package cloudstack
> dpkg-buildpackage: source version 4.10.0.0-SNAPSHOT
> dpkg-buildpackage: source distribution unstable
> dpkg-buildpackage: source changed by the Apache CloudStack project <
> dev@cloudstack.apache.org>
> dpkg-buildpackage: host architecture amd64
> dpkg-source --before-build cloudstack
> dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 9)
> python-mysql.connector dh-systemd
> dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
> aborting
> dpkg-buildpackage: warning: (Use -d flag to override.)
>
>
> On Mon, May 22, 2017 at 9:59 PM, sachin patil 
> >
> wrote:
>
>> I am stuck in rain.
>> thanks for the info sir. will do all relevant checks and mail you in an
>> hour
>>
>> On 22-May-2017 9:55 PM, "Syed Ahmed" 
>> > wrote:
>>
>>> FYI, if you find the problem even with latest 4.9 agent. Try building
>>> the debs and install them on the host
>>>
>>> mvn install -P deps && dpkg-buildpackage
>>>
>>>
>>>
>>> On Mon, May 22, 2017 at 10:43 AM, Daan Hoogland 
>>> 
>>> > wrote:
>>>
 On Mon, May 22, 2017 at 4:37 PM, sachin patil 
 >
 wrote:
 >
 >> > >> According to the link you told me to enter in acs.list in
 source.d
 >> > >> folder. Cloudstack-agent 4.9.2 is installed.  I build CS
 management
 >> from
 >> > >> code 4.10.0.0 snapshot.


 You better have a look at this. Does the agent and the ms both support
 (the same version of) that setup host params command? something might
 have changed between 4.9.2 and 4.10 snapshot.

 --
 Daan

>>>
>>>
>

rohit.ya...@shapeblue.com
www.shapeblue.com
@shapeblue




rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: GSoC'17

[sachin patil]

Hello rohit,


Yesterday I tried to install all dependencies . I have installed all
dependencies you mentioned expect Python - MySQL.connector. I have
installed it using  sudo apt-get python-mysql.connector it installs
successfully . But if I try to package it after using ./build-deb.sh it
still says Python MySQL connector dependency unmet

I am trying to solve this right now

On 23-May-2017 1:57 PM, "Rohit Yadav"  wrote:

> Sachin,
>
>
> I think you're trying to build deb packages. To do this on your
> Ubuntu16.04 based environment, install the build dependencies as defined in
> the *debian/control* file (apt-get install them)
>
>
> *Build-Depends: debhelper (>= 9), openjdk-8-jdk | java8-sdk | java8-jdk |
> openjdk-7-jdk, genisoimage,*
> * python-mysql.connector, maven (>= 3) | maven3, python (>= 2.7),
> lsb-release, dh-systemd*
>
> You may also consider to use a docker container image I had created for
> this purpose, we use this container in all of the blueorangutan-trillian CI
> tests:
>
> https://hub.docker.com/r/bhaisaab/ubuntu-cloudstack-slave/
>
> Reference deb-pkg build script using above docker container: https://gist.
> github.com/rhtyd/57c5b904c1f25455126cbc6b1c0bb83f
>
>
> Regards.
> --
> *From:* sachin patil 
> *Sent:* 22 May 2017 23:50:13
> *To:* Syed Ahmed
> *Cc:* dev
> *Subject:* Re: GSoC'17
>
> Hello,
>
> Sry to be late. The output of the first command mvn install -P deps
> https://drive.google.com/file/d/0B250zd28Pn8WWklXdVdHZGdyVzg/
> view?usp=sharing
>
> output of second command dpkg-buildpackage
>
> dpkg-buildpackage: source package cloudstack
> dpkg-buildpackage: source version 4.10.0.0-SNAPSHOT
> dpkg-buildpackage: source distribution unstable
> dpkg-buildpackage: source changed by the Apache CloudStack project <
> dev@cloudstack.apache.org>
> dpkg-buildpackage: host architecture amd64
> dpkg-source --before-build cloudstack
> dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 9)
> python-mysql.connector dh-systemd
> dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
> aborting
> dpkg-buildpackage: warning: (Use -d flag to override.)
>
> On Mon, May 22, 2017 at 11:47 PM, sachin patil 
> wrote:
>
> > Hello,
> >
> > Sry to be late. The output of the first command mvn install -P deps
> > attached in the mail.
> >
> > output of second command dpkg-buildpackage
> >
> > dpkg-buildpackage: source package cloudstack
> > dpkg-buildpackage: source version 4.10.0.0-SNAPSHOT
> > dpkg-buildpackage: source distribution unstable
> > dpkg-buildpackage: source changed by the Apache CloudStack project <
> > dev@cloudstack.apache.org>
> > dpkg-buildpackage: host architecture amd64
> > dpkg-source --before-build cloudstack
> > dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 9)
> > python-mysql.connector dh-systemd
> > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
> > aborting
> > dpkg-buildpackage: warning: (Use -d flag to override.)
> >
> >
> > On Mon, May 22, 2017 at 9:59 PM, sachin patil 
> > wrote:
> >
> >> I am stuck in rain.
> >> thanks for the info sir. will do all relevant checks and mail you in an
> >> hour
> >>
> >> On 22-May-2017 9:55 PM, "Syed Ahmed"  wrote:
> >>
> >>> FYI, if you find the problem even with latest 4.9 agent. Try building
> >>> the debs and install them on the host
> >>>
> >>> mvn install -P deps && dpkg-buildpackage
> >>>
> >>>
> >>>
> >>> On Mon, May 22, 2017 at 10:43 AM, Daan Hoogland <
> daan.hoogl...@gmail.com
> >>> > wrote:
> >>>
>  On Mon, May 22, 2017 at 4:37 PM, sachin patil  >
>  wrote:
>  >
>  >> > >> According to the link you told me to enter in acs.list in
>  source.d
>  >> > >> folder. Cloudstack-agent 4.9.2 is installed.  I build CS
>  management
>  >> from
>  >> > >> code 4.10.0.0 snapshot.
> 
> 
>  You better have a look at this. Does the agent and the ms both support
>  (the same version of) that setup host params command? something might
>  have changed between 4.9.2 and 4.10 snapshot.
> 
>  --
>  Daan
> 
> >>>
> >>>
> >
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
>
>
>

Re: GSoC'17

[Rohit Yadav]

Sachin,


I think you're trying to build deb packages. To do this on your Ubuntu16.04 
based environment, install the build dependencies as defined in the 
debian/control file (apt-get install them)

Build-Depends: debhelper (>= 9), openjdk-8-jdk | java8-sdk | java8-jdk | 
openjdk-7-jdk, genisoimage,
 python-mysql.connector, maven (>= 3) | maven3, python (>= 2.7), lsb-release, 
dh-systemd


You may also consider to use a docker container image I had created for this 
purpose, we use this container in all of the blueorangutan-trillian CI tests:

https://hub.docker.com/r/bhaisaab/ubuntu-cloudstack-slave/


Reference deb-pkg build script using above docker container: 
https://gist.github.com/rhtyd/57c5b904c1f25455126cbc6b1c0bb83f


Regards.


From: sachin patil 
Sent: 22 May 2017 23:50:13
To: Syed Ahmed
Cc: dev
Subject: Re: GSoC'17

Hello,

Sry to be late. The output of the first command mvn install -P deps
https://drive.google.com/file/d/0B250zd28Pn8WWklXdVdHZGdyVzg/view?usp=sharing

output of second command dpkg-buildpackage

dpkg-buildpackage: source package cloudstack
dpkg-buildpackage: source version 4.10.0.0-SNAPSHOT
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by the Apache CloudStack project <
dev@cloudstack.apache.org>
dpkg-buildpackage: host architecture amd64
dpkg-source --before-build cloudstack
dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 9)
python-mysql.connector dh-systemd
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
aborting
dpkg-buildpackage: warning: (Use -d flag to override.)

On Mon, May 22, 2017 at 11:47 PM, sachin patil 
wrote:

> Hello,
>
> Sry to be late. The output of the first command mvn install -P deps
> attached in the mail.
>
> output of second command dpkg-buildpackage
>
> dpkg-buildpackage: source package cloudstack
> dpkg-buildpackage: source version 4.10.0.0-SNAPSHOT
> dpkg-buildpackage: source distribution unstable
> dpkg-buildpackage: source changed by the Apache CloudStack project <
> dev@cloudstack.apache.org>
> dpkg-buildpackage: host architecture amd64
> dpkg-source --before-build cloudstack
> dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 9)
> python-mysql.connector dh-systemd
> dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
> aborting
> dpkg-buildpackage: warning: (Use -d flag to override.)
>
>
> On Mon, May 22, 2017 at 9:59 PM, sachin patil 
> wrote:
>
>> I am stuck in rain.
>> thanks for the info sir. will do all relevant checks and mail you in an
>> hour
>>
>> On 22-May-2017 9:55 PM, "Syed Ahmed"  wrote:
>>
>>> FYI, if you find the problem even with latest 4.9 agent. Try building
>>> the debs and install them on the host
>>>
>>> mvn install -P deps && dpkg-buildpackage
>>>
>>>
>>>
>>> On Mon, May 22, 2017 at 10:43 AM, Daan Hoogland >> > wrote:
>>>
 On Mon, May 22, 2017 at 4:37 PM, sachin patil 
 wrote:
 >
 >> > >> According to the link you told me to enter in acs.list in
 source.d
 >> > >> folder. Cloudstack-agent 4.9.2 is installed.  I build CS
 management
 >> from
 >> > >> code 4.10.0.0 snapshot.


 You better have a look at this. Does the agent and the ms both support
 (the same version of) that setup host params command? something might
 have changed between 4.9.2 and 4.10 snapshot.

 --
 Daan

>>>
>>>
>

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue