You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Chip Childers <ch...@sungard.com> on 2012/10/24 23:56:39 UTC
Moving beyond 4.0.0-incubating
Hi all,
Obviously we still have to actually pass a vote, and then pass another
vote within the IPMC, before we can call success with
4.0.0-incubating. (And we may have to do this several more times,
depending on how things go.) However, I think it's time to catch up
on work that's ongoing, ideas for what to do next, and to start to
plan out what our next community goals are.
Along those lines, perhaps we can all start communicating a little
better about where other work stands? I'd like to ask folks that are
working on features / tools to kick off discussion threads for their
specific areas. Questions that would be great to have answered
include: How's the work going generally? Are there any design
decisions that should be talked about? Any help needed?
Examples that come to mind (in no order, and not exhaustive):
1- Adding more plugin capabilities to the core design (I assume this
is what the javelin branch is for)
2- RBAC
3 - Event handling / message bus integration
4 - DevCloud changes
5 - Work demonstrated at Citrix Synergy (Cisco product integrations)
6 - Auto-scaling
7 - Host deployment feature
I'd also like to ask that we start proposing new features to the list
again (I know that some of this has continued, but I think it died
down a bit). It's going to be important to start thinking about
timing of our next feature release soon (and to be time bound about
it), so I think we need to ensure that we're all sharing current
thoughts, status, etc... And as always, feel free to let me know if
you disagree!
Thanks all,
-chip
Re: Moving beyond 4.0.0-incubating
Posted by Chiradeep Vittal <Ch...@citrix.com>.
I guess we should all be updating this:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Next+Rele
ase
And write an FS for the feature
On 10/29/12 11:23 AM, "Chiradeep Vittal" <Ch...@citrix.com>
wrote:
>I am going to start working on unentangling some of the network
>orchestration to make the orchestration piece more modular.
>At the end of it, I hope to have a 'simplified' network offering that out
>of the box does not involve any system vms.
>The benefits will be:
> - easier to understand the core network orchestration
> - easier to replace the default virtual router
> - greater testability
>
>In parallel, I will be working on integrating Cisco's virtual firewall
>ASA1000v as a replacement for the virtual router, but that is a stretch
>goal.
>
>
>On 10/29/12 12:37 AM, "Hugo Trippaers" <HT...@schubergphilis.com>
>wrote:
>
>>
>>I'm working on
>> * Nicira support for SourceNat, StaticNat and PortForwarding
>> * Maven improvements
>> * Rpm packaging sample using maven buildsystem
>>
>>And of course bug finding and fixing whiel we are building our cloudstack
>>cloud for our customers.
>>
>>Cheers,
>>
>>Hugo
>>
>>> -----Original Message-----
>>> From: Kelceydamage@bbits [mailto:kelcey@bbits.ca]
>>> Sent: Saturday, October 27, 2012 7:25 PM
>>> To: cloudstack-dev@incubator.apache.org
>>> Cc: cloudstack-dev@incubator.apache.org
>>> Subject: Re: Moving beyond 4.0.0-incubating
>>>
>>> A python agent is something I would really like. And also is a project
>>>I might
>>> actually be able to work on(Python is my primary language).
>>>
>>> Let me know when you get this going and I will do what I can to assist.
>>>
>>> Sent from my iPhone
>>>
>>> On Oct 27, 2012, at 2:44 AM, Rohit Yadav <ro...@citrix.com>
>>>wrote:
>>>
>>> > Hi,
>>> >
>>> > I'm too working on the client based on marvin too
>>> (https://issues.apache.org/jira/browse/CLOUDSTACK-132), pl. see the
>>> comments on the issue so we can collaborate on this.
>>> > Next thing I want to discuss and work on is the agent for KVM.
>>> >
>>> > Right now if one install agent on KVM; he had to:
>>> > - Do it manually on all hosts (not scalable unless some provisioning
>>> > tool, like chef/puppet is used); required installation of
>>>dependencies
>>> > - Upgrade is manual; properties are stored on host; possibility of
>>> > loss of these files while upgrade (if upgrade/install scenarios are
>>> > not very well handled)
>>> > - Developer development is manual and not smooth; if you change
>>> > something in agent code, you are required to manually setup agent on
>>> > hosts
>>> >
>>> > Proposed agent:
>>> > - Mgmt server should ssh and setup the agent; in case of Xen, vmops
>>> > plugin which is written in Python is deployed and used (much easier
>>>as
>>> > they have xapi service and we're just adding one plugin)
>>> > - Possibly rewrite agent in Python because:
>>> > * Present agent written in Java, comes with its own baggage,
>>>required
>>> openjdk etc.
>>> > * Python is preinstalled on most Linux distros
>>> > * Writing in Python makes it easy to hack, no hack-build-run loop;
>>> > just hack-run
>>> > * Agent can have it's own environment and run in a virtualenv; the
>>> > present agent required deps etc. which are not local to the agent,
>>>but
>>> > affects the system in general
>>> > * Can reuse libvirt-python (no virsh), example code I'd written in
>>> > past;
>>> >
>>>https://github.com/bhaisaab/vmcontroller/blob/master/src/vmcontroller.
>>> > host/vmcontroller/host/controller/hypervisors/LibVirt.py
>>> > - Rewriting and throwing away code can be a wild ide, so if we decide
>>> > to not rewrite it, let's discuss some way to automate agent
>>>deployment
>>> > on hosts and make it easier for developers to work with it
>>> >
>>> > Regards.
>>> >
>>> > ________________________________________
>>> > From: Sebastien Goasguen [runseb@gmail.com]
>>> > Sent: Saturday, October 27, 2012 2:27 PM
>>> > To: cloudstack-dev@incubator.apache.org
>>> > Subject: Re: Moving beyond 4.0.0-incubating
>>> >
>>> > Hi,
>>> >
>>> > *I emailed with James Martin who has been doing some devcloud
>>> improvements, I encouraged him to submit his patches even if it's not
>>>done.
>>> >
>>> > *Prasanna created a marvin-parallel branch to host a threading of the
>>> integration tests. I will get back to that after the vote.
>>> >
>>> > *There is a request for an interactive shell. I just tried
>>>jclouds-cli, it's nice
>>> but is far from covering all cloudstack can do. So I am starting a
>>>prototype
>>> using the marvin cloudstackAPI.
>>> >
>>> > *There is also an important thread on a better AWS support with a
>>>newer
>>> api version.
>>> >
>>> > On the more technical front, I think we need to look at network
>>> > capabilities that are only available with netscaler and provide an
>>> > open source alternative. Potentially also look at integrating quantum
>>> > -if you look at it as an open source nicira-
>>> >
>>> > -Sebastien
>>> >
>>> >
>>> > On Oct 26, 2012, at 10:07 PM, Edison Su <Ed...@citrix.com> wrote:
>>> >
>>> >> I am working on the storage subsystem refactor on javelin branch.
>>>The
>>> code I write is under platform/storage directory. I'll send out a
>>>detailed
>>> changes I want to make in the next few days.
>>> >>
>>> >>> -----Original Message-----
>>> >>> From: Chip Childers [mailto:chip.childers@sungard.com]
>>> >>> Sent: Wednesday, October 24, 2012 2:57 PM
>>> >>> To: cloudstack-dev@incubator.apache.org
>>> >>> Subject: Moving beyond 4.0.0-incubating
>>> >>>
>>> >>> Hi all,
>>> >>>
>>> >>> Obviously we still have to actually pass a vote, and then pass
>>> >>> another vote within the IPMC, before we can call success with
>>> >>> 4.0.0-incubating. (And we may have to do this several more times,
>>> >>> depending on how things go.) However, I think it's time to catch
>>>up
>>> >>> on work that's ongoing, ideas for what to do next, and to start to
>>> >>> plan out what our next community goals are.
>>> >>>
>>> >>> Along those lines, perhaps we can all start communicating a little
>>> >>> better about where other work stands? I'd like to ask folks that
>>> >>> are working on features / tools to kick off discussion threads for
>>> >>> their specific areas. Questions that would be great to have
>>> >>> answered
>>> >>> include: How's the work going generally? Are there any design
>>> >>> decisions that should be talked about? Any help needed?
>>> >>>
>>> >>> Examples that come to mind (in no order, and not exhaustive):
>>> >>>
>>> >>> 1- Adding more plugin capabilities to the core design (I assume
>>>this
>>> >>> is what the javelin branch is for)
>>> >>> 2- RBAC
>>> >>> 3 - Event handling / message bus integration
>>> >>> 4 - DevCloud changes
>>> >>> 5 - Work demonstrated at Citrix Synergy (Cisco product
>>>integrations)
>>> >>> 6 - Auto-scaling
>>> >>> 7 - Host deployment feature
>>> >>>
>>> >>> I'd also like to ask that we start proposing new features to the
>>> >>> list again (I know that some of this has continued, but I think it
>>> >>> died down a bit). It's going to be important to start thinking
>>> >>> about timing of our next feature release soon (and to be time bound
>>> >>> about it), so I think we need to ensure that we're all sharing
>>> >>> current thoughts, status, etc... And as always, feel free to let
>>>me
>>> >>> know if you disagree!
>>> >>>
>>> >>> Thanks all,
>>> >>>
>>> >>> -chip
>>> >
>
Re: Moving beyond 4.0.0-incubating
Posted by Chiradeep Vittal <Ch...@citrix.com>.
I am going to start working on unentangling some of the network
orchestration to make the orchestration piece more modular.
At the end of it, I hope to have a 'simplified' network offering that out
of the box does not involve any system vms.
The benefits will be:
- easier to understand the core network orchestration
- easier to replace the default virtual router
- greater testability
In parallel, I will be working on integrating Cisco's virtual firewall
ASA1000v as a replacement for the virtual router, but that is a stretch
goal.
On 10/29/12 12:37 AM, "Hugo Trippaers" <HT...@schubergphilis.com>
wrote:
>
>I'm working on
> * Nicira support for SourceNat, StaticNat and PortForwarding
> * Maven improvements
> * Rpm packaging sample using maven buildsystem
>
>And of course bug finding and fixing whiel we are building our cloudstack
>cloud for our customers.
>
>Cheers,
>
>Hugo
>
>> -----Original Message-----
>> From: Kelceydamage@bbits [mailto:kelcey@bbits.ca]
>> Sent: Saturday, October 27, 2012 7:25 PM
>> To: cloudstack-dev@incubator.apache.org
>> Cc: cloudstack-dev@incubator.apache.org
>> Subject: Re: Moving beyond 4.0.0-incubating
>>
>> A python agent is something I would really like. And also is a project
>>I might
>> actually be able to work on(Python is my primary language).
>>
>> Let me know when you get this going and I will do what I can to assist.
>>
>> Sent from my iPhone
>>
>> On Oct 27, 2012, at 2:44 AM, Rohit Yadav <ro...@citrix.com> wrote:
>>
>> > Hi,
>> >
>> > I'm too working on the client based on marvin too
>> (https://issues.apache.org/jira/browse/CLOUDSTACK-132), pl. see the
>> comments on the issue so we can collaborate on this.
>> > Next thing I want to discuss and work on is the agent for KVM.
>> >
>> > Right now if one install agent on KVM; he had to:
>> > - Do it manually on all hosts (not scalable unless some provisioning
>> > tool, like chef/puppet is used); required installation of dependencies
>> > - Upgrade is manual; properties are stored on host; possibility of
>> > loss of these files while upgrade (if upgrade/install scenarios are
>> > not very well handled)
>> > - Developer development is manual and not smooth; if you change
>> > something in agent code, you are required to manually setup agent on
>> > hosts
>> >
>> > Proposed agent:
>> > - Mgmt server should ssh and setup the agent; in case of Xen, vmops
>> > plugin which is written in Python is deployed and used (much easier as
>> > they have xapi service and we're just adding one plugin)
>> > - Possibly rewrite agent in Python because:
>> > * Present agent written in Java, comes with its own baggage, required
>> openjdk etc.
>> > * Python is preinstalled on most Linux distros
>> > * Writing in Python makes it easy to hack, no hack-build-run loop;
>> > just hack-run
>> > * Agent can have it's own environment and run in a virtualenv; the
>> > present agent required deps etc. which are not local to the agent, but
>> > affects the system in general
>> > * Can reuse libvirt-python (no virsh), example code I'd written in
>> > past;
>> > https://github.com/bhaisaab/vmcontroller/blob/master/src/vmcontroller.
>> > host/vmcontroller/host/controller/hypervisors/LibVirt.py
>> > - Rewriting and throwing away code can be a wild ide, so if we decide
>> > to not rewrite it, let's discuss some way to automate agent deployment
>> > on hosts and make it easier for developers to work with it
>> >
>> > Regards.
>> >
>> > ________________________________________
>> > From: Sebastien Goasguen [runseb@gmail.com]
>> > Sent: Saturday, October 27, 2012 2:27 PM
>> > To: cloudstack-dev@incubator.apache.org
>> > Subject: Re: Moving beyond 4.0.0-incubating
>> >
>> > Hi,
>> >
>> > *I emailed with James Martin who has been doing some devcloud
>> improvements, I encouraged him to submit his patches even if it's not
>>done.
>> >
>> > *Prasanna created a marvin-parallel branch to host a threading of the
>> integration tests. I will get back to that after the vote.
>> >
>> > *There is a request for an interactive shell. I just tried
>>jclouds-cli, it's nice
>> but is far from covering all cloudstack can do. So I am starting a
>>prototype
>> using the marvin cloudstackAPI.
>> >
>> > *There is also an important thread on a better AWS support with a
>>newer
>> api version.
>> >
>> > On the more technical front, I think we need to look at network
>> > capabilities that are only available with netscaler and provide an
>> > open source alternative. Potentially also look at integrating quantum
>> > -if you look at it as an open source nicira-
>> >
>> > -Sebastien
>> >
>> >
>> > On Oct 26, 2012, at 10:07 PM, Edison Su <Ed...@citrix.com> wrote:
>> >
>> >> I am working on the storage subsystem refactor on javelin branch. The
>> code I write is under platform/storage directory. I'll send out a
>>detailed
>> changes I want to make in the next few days.
>> >>
>> >>> -----Original Message-----
>> >>> From: Chip Childers [mailto:chip.childers@sungard.com]
>> >>> Sent: Wednesday, October 24, 2012 2:57 PM
>> >>> To: cloudstack-dev@incubator.apache.org
>> >>> Subject: Moving beyond 4.0.0-incubating
>> >>>
>> >>> Hi all,
>> >>>
>> >>> Obviously we still have to actually pass a vote, and then pass
>> >>> another vote within the IPMC, before we can call success with
>> >>> 4.0.0-incubating. (And we may have to do this several more times,
>> >>> depending on how things go.) However, I think it's time to catch up
>> >>> on work that's ongoing, ideas for what to do next, and to start to
>> >>> plan out what our next community goals are.
>> >>>
>> >>> Along those lines, perhaps we can all start communicating a little
>> >>> better about where other work stands? I'd like to ask folks that
>> >>> are working on features / tools to kick off discussion threads for
>> >>> their specific areas. Questions that would be great to have
>> >>> answered
>> >>> include: How's the work going generally? Are there any design
>> >>> decisions that should be talked about? Any help needed?
>> >>>
>> >>> Examples that come to mind (in no order, and not exhaustive):
>> >>>
>> >>> 1- Adding more plugin capabilities to the core design (I assume this
>> >>> is what the javelin branch is for)
>> >>> 2- RBAC
>> >>> 3 - Event handling / message bus integration
>> >>> 4 - DevCloud changes
>> >>> 5 - Work demonstrated at Citrix Synergy (Cisco product integrations)
>> >>> 6 - Auto-scaling
>> >>> 7 - Host deployment feature
>> >>>
>> >>> I'd also like to ask that we start proposing new features to the
>> >>> list again (I know that some of this has continued, but I think it
>> >>> died down a bit). It's going to be important to start thinking
>> >>> about timing of our next feature release soon (and to be time bound
>> >>> about it), so I think we need to ensure that we're all sharing
>> >>> current thoughts, status, etc... And as always, feel free to let me
>> >>> know if you disagree!
>> >>>
>> >>> Thanks all,
>> >>>
>> >>> -chip
>> >
RE: Moving beyond 4.0.0-incubating
Posted by Hugo Trippaers <HT...@schubergphilis.com>.
I'm working on
* Nicira support for SourceNat, StaticNat and PortForwarding
* Maven improvements
* Rpm packaging sample using maven buildsystem
And of course bug finding and fixing whiel we are building our cloudstack cloud for our customers.
Cheers,
Hugo
> -----Original Message-----
> From: Kelceydamage@bbits [mailto:kelcey@bbits.ca]
> Sent: Saturday, October 27, 2012 7:25 PM
> To: cloudstack-dev@incubator.apache.org
> Cc: cloudstack-dev@incubator.apache.org
> Subject: Re: Moving beyond 4.0.0-incubating
>
> A python agent is something I would really like. And also is a project I might
> actually be able to work on(Python is my primary language).
>
> Let me know when you get this going and I will do what I can to assist.
>
> Sent from my iPhone
>
> On Oct 27, 2012, at 2:44 AM, Rohit Yadav <ro...@citrix.com> wrote:
>
> > Hi,
> >
> > I'm too working on the client based on marvin too
> (https://issues.apache.org/jira/browse/CLOUDSTACK-132), pl. see the
> comments on the issue so we can collaborate on this.
> > Next thing I want to discuss and work on is the agent for KVM.
> >
> > Right now if one install agent on KVM; he had to:
> > - Do it manually on all hosts (not scalable unless some provisioning
> > tool, like chef/puppet is used); required installation of dependencies
> > - Upgrade is manual; properties are stored on host; possibility of
> > loss of these files while upgrade (if upgrade/install scenarios are
> > not very well handled)
> > - Developer development is manual and not smooth; if you change
> > something in agent code, you are required to manually setup agent on
> > hosts
> >
> > Proposed agent:
> > - Mgmt server should ssh and setup the agent; in case of Xen, vmops
> > plugin which is written in Python is deployed and used (much easier as
> > they have xapi service and we're just adding one plugin)
> > - Possibly rewrite agent in Python because:
> > * Present agent written in Java, comes with its own baggage, required
> openjdk etc.
> > * Python is preinstalled on most Linux distros
> > * Writing in Python makes it easy to hack, no hack-build-run loop;
> > just hack-run
> > * Agent can have it's own environment and run in a virtualenv; the
> > present agent required deps etc. which are not local to the agent, but
> > affects the system in general
> > * Can reuse libvirt-python (no virsh), example code I'd written in
> > past;
> > https://github.com/bhaisaab/vmcontroller/blob/master/src/vmcontroller.
> > host/vmcontroller/host/controller/hypervisors/LibVirt.py
> > - Rewriting and throwing away code can be a wild ide, so if we decide
> > to not rewrite it, let's discuss some way to automate agent deployment
> > on hosts and make it easier for developers to work with it
> >
> > Regards.
> >
> > ________________________________________
> > From: Sebastien Goasguen [runseb@gmail.com]
> > Sent: Saturday, October 27, 2012 2:27 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: Re: Moving beyond 4.0.0-incubating
> >
> > Hi,
> >
> > *I emailed with James Martin who has been doing some devcloud
> improvements, I encouraged him to submit his patches even if it's not done.
> >
> > *Prasanna created a marvin-parallel branch to host a threading of the
> integration tests. I will get back to that after the vote.
> >
> > *There is a request for an interactive shell. I just tried jclouds-cli, it's nice
> but is far from covering all cloudstack can do. So I am starting a prototype
> using the marvin cloudstackAPI.
> >
> > *There is also an important thread on a better AWS support with a newer
> api version.
> >
> > On the more technical front, I think we need to look at network
> > capabilities that are only available with netscaler and provide an
> > open source alternative. Potentially also look at integrating quantum
> > -if you look at it as an open source nicira-
> >
> > -Sebastien
> >
> >
> > On Oct 26, 2012, at 10:07 PM, Edison Su <Ed...@citrix.com> wrote:
> >
> >> I am working on the storage subsystem refactor on javelin branch. The
> code I write is under platform/storage directory. I'll send out a detailed
> changes I want to make in the next few days.
> >>
> >>> -----Original Message-----
> >>> From: Chip Childers [mailto:chip.childers@sungard.com]
> >>> Sent: Wednesday, October 24, 2012 2:57 PM
> >>> To: cloudstack-dev@incubator.apache.org
> >>> Subject: Moving beyond 4.0.0-incubating
> >>>
> >>> Hi all,
> >>>
> >>> Obviously we still have to actually pass a vote, and then pass
> >>> another vote within the IPMC, before we can call success with
> >>> 4.0.0-incubating. (And we may have to do this several more times,
> >>> depending on how things go.) However, I think it's time to catch up
> >>> on work that's ongoing, ideas for what to do next, and to start to
> >>> plan out what our next community goals are.
> >>>
> >>> Along those lines, perhaps we can all start communicating a little
> >>> better about where other work stands? I'd like to ask folks that
> >>> are working on features / tools to kick off discussion threads for
> >>> their specific areas. Questions that would be great to have
> >>> answered
> >>> include: How's the work going generally? Are there any design
> >>> decisions that should be talked about? Any help needed?
> >>>
> >>> Examples that come to mind (in no order, and not exhaustive):
> >>>
> >>> 1- Adding more plugin capabilities to the core design (I assume this
> >>> is what the javelin branch is for)
> >>> 2- RBAC
> >>> 3 - Event handling / message bus integration
> >>> 4 - DevCloud changes
> >>> 5 - Work demonstrated at Citrix Synergy (Cisco product integrations)
> >>> 6 - Auto-scaling
> >>> 7 - Host deployment feature
> >>>
> >>> I'd also like to ask that we start proposing new features to the
> >>> list again (I know that some of this has continued, but I think it
> >>> died down a bit). It's going to be important to start thinking
> >>> about timing of our next feature release soon (and to be time bound
> >>> about it), so I think we need to ensure that we're all sharing
> >>> current thoughts, status, etc... And as always, feel free to let me
> >>> know if you disagree!
> >>>
> >>> Thanks all,
> >>>
> >>> -chip
> >
Re: Moving beyond 4.0.0-incubating
Posted by "Kelceydamage@bbits" <ke...@bbits.ca>.
A python agent is something I would really like. And also is a project I might actually be able to work on(Python is my primary language).
Let me know when you get this going and I will do what I can to assist.
Sent from my iPhone
On Oct 27, 2012, at 2:44 AM, Rohit Yadav <ro...@citrix.com> wrote:
> Hi,
>
> I'm too working on the client based on marvin too (https://issues.apache.org/jira/browse/CLOUDSTACK-132), pl. see the comments on the issue so we can collaborate on this.
> Next thing I want to discuss and work on is the agent for KVM.
>
> Right now if one install agent on KVM; he had to:
> - Do it manually on all hosts (not scalable unless some provisioning tool, like chef/puppet is used); required installation of dependencies
> - Upgrade is manual; properties are stored on host; possibility of loss of these files while upgrade (if upgrade/install scenarios are not very well handled)
> - Developer development is manual and not smooth; if you change something in agent code, you are required to manually setup agent on hosts
>
> Proposed agent:
> - Mgmt server should ssh and setup the agent; in case of Xen, vmops plugin which is written in Python is deployed and used (much easier as they have xapi service and we're just adding one plugin)
> - Possibly rewrite agent in Python because:
> * Present agent written in Java, comes with its own baggage, required openjdk etc.
> * Python is preinstalled on most Linux distros
> * Writing in Python makes it easy to hack, no hack-build-run loop; just hack-run
> * Agent can have it's own environment and run in a virtualenv; the present agent required deps etc. which are not local to the agent, but affects the system in general
> * Can reuse libvirt-python (no virsh), example code I'd written in past; https://github.com/bhaisaab/vmcontroller/blob/master/src/vmcontroller.host/vmcontroller/host/controller/hypervisors/LibVirt.py
> - Rewriting and throwing away code can be a wild ide, so if we decide to not rewrite it, let's discuss some way to automate agent deployment on hosts and make it easier for developers to work with it
>
> Regards.
>
> ________________________________________
> From: Sebastien Goasguen [runseb@gmail.com]
> Sent: Saturday, October 27, 2012 2:27 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Moving beyond 4.0.0-incubating
>
> Hi,
>
> *I emailed with James Martin who has been doing some devcloud improvements, I encouraged him to submit his patches even if it's not done.
>
> *Prasanna created a marvin-parallel branch to host a threading of the integration tests. I will get back to that after the vote.
>
> *There is a request for an interactive shell. I just tried jclouds-cli, it's nice but is far from covering all cloudstack can do. So I am starting a prototype using the marvin cloudstackAPI.
>
> *There is also an important thread on a better AWS support with a newer api version.
>
> On the more technical front, I think we need to look at network capabilities that are only available with netscaler and provide an open source alternative. Potentially also look at integrating quantum -if you look at it as an open source nicira-
>
> -Sebastien
>
>
> On Oct 26, 2012, at 10:07 PM, Edison Su <Ed...@citrix.com> wrote:
>
>> I am working on the storage subsystem refactor on javelin branch. The code I write is under platform/storage directory. I'll send out a detailed changes I want to make in the next few days.
>>
>>> -----Original Message-----
>>> From: Chip Childers [mailto:chip.childers@sungard.com]
>>> Sent: Wednesday, October 24, 2012 2:57 PM
>>> To: cloudstack-dev@incubator.apache.org
>>> Subject: Moving beyond 4.0.0-incubating
>>>
>>> Hi all,
>>>
>>> Obviously we still have to actually pass a vote, and then pass another
>>> vote within the IPMC, before we can call success with
>>> 4.0.0-incubating. (And we may have to do this several more times,
>>> depending on how things go.) However, I think it's time to catch up
>>> on work that's ongoing, ideas for what to do next, and to start to
>>> plan out what our next community goals are.
>>>
>>> Along those lines, perhaps we can all start communicating a little
>>> better about where other work stands? I'd like to ask folks that are
>>> working on features / tools to kick off discussion threads for their
>>> specific areas. Questions that would be great to have answered
>>> include: How's the work going generally? Are there any design
>>> decisions that should be talked about? Any help needed?
>>>
>>> Examples that come to mind (in no order, and not exhaustive):
>>>
>>> 1- Adding more plugin capabilities to the core design (I assume this
>>> is what the javelin branch is for)
>>> 2- RBAC
>>> 3 - Event handling / message bus integration
>>> 4 - DevCloud changes
>>> 5 - Work demonstrated at Citrix Synergy (Cisco product integrations)
>>> 6 - Auto-scaling
>>> 7 - Host deployment feature
>>>
>>> I'd also like to ask that we start proposing new features to the list
>>> again (I know that some of this has continued, but I think it died
>>> down a bit). It's going to be important to start thinking about
>>> timing of our next feature release soon (and to be time bound about
>>> it), so I think we need to ensure that we're all sharing current
>>> thoughts, status, etc... And as always, feel free to let me know if
>>> you disagree!
>>>
>>> Thanks all,
>>>
>>> -chip
>
RE: Moving beyond 4.0.0-incubating
Posted by Rohit Yadav <ro...@citrix.com>.
Hi,
I'm too working on the client based on marvin too (https://issues.apache.org/jira/browse/CLOUDSTACK-132), pl. see the comments on the issue so we can collaborate on this.
Next thing I want to discuss and work on is the agent for KVM.
Right now if one install agent on KVM; he had to:
- Do it manually on all hosts (not scalable unless some provisioning tool, like chef/puppet is used); required installation of dependencies
- Upgrade is manual; properties are stored on host; possibility of loss of these files while upgrade (if upgrade/install scenarios are not very well handled)
- Developer development is manual and not smooth; if you change something in agent code, you are required to manually setup agent on hosts
Proposed agent:
- Mgmt server should ssh and setup the agent; in case of Xen, vmops plugin which is written in Python is deployed and used (much easier as they have xapi service and we're just adding one plugin)
- Possibly rewrite agent in Python because:
* Present agent written in Java, comes with its own baggage, required openjdk etc.
* Python is preinstalled on most Linux distros
* Writing in Python makes it easy to hack, no hack-build-run loop; just hack-run
* Agent can have it's own environment and run in a virtualenv; the present agent required deps etc. which are not local to the agent, but affects the system in general
* Can reuse libvirt-python (no virsh), example code I'd written in past; https://github.com/bhaisaab/vmcontroller/blob/master/src/vmcontroller.host/vmcontroller/host/controller/hypervisors/LibVirt.py
- Rewriting and throwing away code can be a wild ide, so if we decide to not rewrite it, let's discuss some way to automate agent deployment on hosts and make it easier for developers to work with it
Regards.
________________________________________
From: Sebastien Goasguen [runseb@gmail.com]
Sent: Saturday, October 27, 2012 2:27 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: Moving beyond 4.0.0-incubating
Hi,
*I emailed with James Martin who has been doing some devcloud improvements, I encouraged him to submit his patches even if it's not done.
*Prasanna created a marvin-parallel branch to host a threading of the integration tests. I will get back to that after the vote.
*There is a request for an interactive shell. I just tried jclouds-cli, it's nice but is far from covering all cloudstack can do. So I am starting a prototype using the marvin cloudstackAPI.
*There is also an important thread on a better AWS support with a newer api version.
On the more technical front, I think we need to look at network capabilities that are only available with netscaler and provide an open source alternative. Potentially also look at integrating quantum -if you look at it as an open source nicira-
-Sebastien
On Oct 26, 2012, at 10:07 PM, Edison Su <Ed...@citrix.com> wrote:
> I am working on the storage subsystem refactor on javelin branch. The code I write is under platform/storage directory. I'll send out a detailed changes I want to make in the next few days.
>
>> -----Original Message-----
>> From: Chip Childers [mailto:chip.childers@sungard.com]
>> Sent: Wednesday, October 24, 2012 2:57 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Moving beyond 4.0.0-incubating
>>
>> Hi all,
>>
>> Obviously we still have to actually pass a vote, and then pass another
>> vote within the IPMC, before we can call success with
>> 4.0.0-incubating. (And we may have to do this several more times,
>> depending on how things go.) However, I think it's time to catch up
>> on work that's ongoing, ideas for what to do next, and to start to
>> plan out what our next community goals are.
>>
>> Along those lines, perhaps we can all start communicating a little
>> better about where other work stands? I'd like to ask folks that are
>> working on features / tools to kick off discussion threads for their
>> specific areas. Questions that would be great to have answered
>> include: How's the work going generally? Are there any design
>> decisions that should be talked about? Any help needed?
>>
>> Examples that come to mind (in no order, and not exhaustive):
>>
>> 1- Adding more plugin capabilities to the core design (I assume this
>> is what the javelin branch is for)
>> 2- RBAC
>> 3 - Event handling / message bus integration
>> 4 - DevCloud changes
>> 5 - Work demonstrated at Citrix Synergy (Cisco product integrations)
>> 6 - Auto-scaling
>> 7 - Host deployment feature
>>
>> I'd also like to ask that we start proposing new features to the list
>> again (I know that some of this has continued, but I think it died
>> down a bit). It's going to be important to start thinking about
>> timing of our next feature release soon (and to be time bound about
>> it), so I think we need to ensure that we're all sharing current
>> thoughts, status, etc... And as always, feel free to let me know if
>> you disagree!
>>
>> Thanks all,
>>
>> -chip
Re: Moving beyond 4.0.0-incubating
Posted by Sebastien Goasguen <ru...@gmail.com>.
Hi,
*I emailed with James Martin who has been doing some devcloud improvements, I encouraged him to submit his patches even if it's not done.
*Prasanna created a marvin-parallel branch to host a threading of the integration tests. I will get back to that after the vote.
*There is a request for an interactive shell. I just tried jclouds-cli, it's nice but is far from covering all cloudstack can do. So I am starting a prototype using the marvin cloudstackAPI.
*There is also an important thread on a better AWS support with a newer api version.
On the more technical front, I think we need to look at network capabilities that are only available with netscaler and provide an open source alternative. Potentially also look at integrating quantum -if you look at it as an open source nicira-
-Sebastien
On Oct 26, 2012, at 10:07 PM, Edison Su <Ed...@citrix.com> wrote:
> I am working on the storage subsystem refactor on javelin branch. The code I write is under platform/storage directory. I'll send out a detailed changes I want to make in the next few days.
>
>> -----Original Message-----
>> From: Chip Childers [mailto:chip.childers@sungard.com]
>> Sent: Wednesday, October 24, 2012 2:57 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Moving beyond 4.0.0-incubating
>>
>> Hi all,
>>
>> Obviously we still have to actually pass a vote, and then pass another
>> vote within the IPMC, before we can call success with
>> 4.0.0-incubating. (And we may have to do this several more times,
>> depending on how things go.) However, I think it's time to catch up
>> on work that's ongoing, ideas for what to do next, and to start to
>> plan out what our next community goals are.
>>
>> Along those lines, perhaps we can all start communicating a little
>> better about where other work stands? I'd like to ask folks that are
>> working on features / tools to kick off discussion threads for their
>> specific areas. Questions that would be great to have answered
>> include: How's the work going generally? Are there any design
>> decisions that should be talked about? Any help needed?
>>
>> Examples that come to mind (in no order, and not exhaustive):
>>
>> 1- Adding more plugin capabilities to the core design (I assume this
>> is what the javelin branch is for)
>> 2- RBAC
>> 3 - Event handling / message bus integration
>> 4 - DevCloud changes
>> 5 - Work demonstrated at Citrix Synergy (Cisco product integrations)
>> 6 - Auto-scaling
>> 7 - Host deployment feature
>>
>> I'd also like to ask that we start proposing new features to the list
>> again (I know that some of this has continued, but I think it died
>> down a bit). It's going to be important to start thinking about
>> timing of our next feature release soon (and to be time bound about
>> it), so I think we need to ensure that we're all sharing current
>> thoughts, status, etc... And as always, feel free to let me know if
>> you disagree!
>>
>> Thanks all,
>>
>> -chip
RE: Moving beyond 4.0.0-incubating
Posted by Edison Su <Ed...@citrix.com>.
I am working on the storage subsystem refactor on javelin branch. The code I write is under platform/storage directory. I'll send out a detailed changes I want to make in the next few days.
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Wednesday, October 24, 2012 2:57 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Moving beyond 4.0.0-incubating
>
> Hi all,
>
> Obviously we still have to actually pass a vote, and then pass another
> vote within the IPMC, before we can call success with
> 4.0.0-incubating. (And we may have to do this several more times,
> depending on how things go.) However, I think it's time to catch up
> on work that's ongoing, ideas for what to do next, and to start to
> plan out what our next community goals are.
>
> Along those lines, perhaps we can all start communicating a little
> better about where other work stands? I'd like to ask folks that are
> working on features / tools to kick off discussion threads for their
> specific areas. Questions that would be great to have answered
> include: How's the work going generally? Are there any design
> decisions that should be talked about? Any help needed?
>
> Examples that come to mind (in no order, and not exhaustive):
>
> 1- Adding more plugin capabilities to the core design (I assume this
> is what the javelin branch is for)
> 2- RBAC
> 3 - Event handling / message bus integration
> 4 - DevCloud changes
> 5 - Work demonstrated at Citrix Synergy (Cisco product integrations)
> 6 - Auto-scaling
> 7 - Host deployment feature
>
> I'd also like to ask that we start proposing new features to the list
> again (I know that some of this has continued, but I think it died
> down a bit). It's going to be important to start thinking about
> timing of our next feature release soon (and to be time bound about
> it), so I think we need to ensure that we're all sharing current
> thoughts, status, etc... And as always, feel free to let me know if
> you disagree!
>
> Thanks all,
>
> -chip
Re: Moving beyond 4.0.0-incubating
Posted by Marcus Sorensen <sh...@gmail.com>.
Well, I've got the resize volumes patch, which I've started an email
thread about, but I think I need to roll it into a functional spec.
I've also got the vlan isolation Q-in-Q thing, which I've written a
draft functional spec for. It's a pretty simple change code wise for
KVM, but I've yet to look at how Xen reacts, or even if they'll need
adjustments to their bridge naming scheme and all that.
On Fri, Oct 26, 2012 at 1:21 PM, Chip Childers
<ch...@sungard.com> wrote:
> On Wed, Oct 24, 2012 at 5:56 PM, Chip Childers
> <ch...@sungard.com> wrote:
>> Hi all,
>>
>> Obviously we still have to actually pass a vote, and then pass another
>> vote within the IPMC, before we can call success with
>> 4.0.0-incubating. (And we may have to do this several more times,
>> depending on how things go.) However, I think it's time to catch up
>> on work that's ongoing, ideas for what to do next, and to start to
>> plan out what our next community goals are.
>>
>> Along those lines, perhaps we can all start communicating a little
>> better about where other work stands? I'd like to ask folks that are
>> working on features / tools to kick off discussion threads for their
>> specific areas. Questions that would be great to have answered
>> include: How's the work going generally? Are there any design
>> decisions that should be talked about? Any help needed?
>>
>> Examples that come to mind (in no order, and not exhaustive):
>>
>> 1- Adding more plugin capabilities to the core design (I assume this
>> is what the javelin branch is for)
>> 2- RBAC
>> 3 - Event handling / message bus integration
>> 4 - DevCloud changes
>> 5 - Work demonstrated at Citrix Synergy (Cisco product integrations)
>> 6 - Auto-scaling
>> 7 - Host deployment feature
>>
>> I'd also like to ask that we start proposing new features to the list
>> again (I know that some of this has continued, but I think it died
>> down a bit). It's going to be important to start thinking about
>> timing of our next feature release soon (and to be time bound about
>> it), so I think we need to ensure that we're all sharing current
>> thoughts, status, etc... And as always, feel free to let me know if
>> you disagree!
>>
>> Thanks all,
>>
>> -chip
>
> So I'll take silence as meaning that folks are heads down working!
> (but I'll start with something from the SunGard team)...
>
> Status of adding Unit Tests:
>
> Yichi started work on a bunch of unit tests for the API project. He
> added 100 tests via his patch submissions. They are currently in the
> junit-test branch, but there are some issues getting them to run
> correctly with Maven (specifically the junit version that is loaded).
> Mani is going to be looking at that, and a he and Meghna are going to
> be adding more tests to that branch. Once we have the test passing,
> I'll merge into master (and hopefully it will jive with the maven
> changes going on there).
>
> Also, we're preparing a couple of feature proposals right now, which
> we obviously want to get reviewed by the community before proceeding.
> Expect them to start showing up in the next week or two.
>
> Looking forward to updates from others!
>
> -chip
Re: Moving beyond 4.0.0-incubating
Posted by Chip Childers <ch...@sungard.com>.
On Wed, Oct 24, 2012 at 5:56 PM, Chip Childers
<ch...@sungard.com> wrote:
> Hi all,
>
> Obviously we still have to actually pass a vote, and then pass another
> vote within the IPMC, before we can call success with
> 4.0.0-incubating. (And we may have to do this several more times,
> depending on how things go.) However, I think it's time to catch up
> on work that's ongoing, ideas for what to do next, and to start to
> plan out what our next community goals are.
>
> Along those lines, perhaps we can all start communicating a little
> better about where other work stands? I'd like to ask folks that are
> working on features / tools to kick off discussion threads for their
> specific areas. Questions that would be great to have answered
> include: How's the work going generally? Are there any design
> decisions that should be talked about? Any help needed?
>
> Examples that come to mind (in no order, and not exhaustive):
>
> 1- Adding more plugin capabilities to the core design (I assume this
> is what the javelin branch is for)
> 2- RBAC
> 3 - Event handling / message bus integration
> 4 - DevCloud changes
> 5 - Work demonstrated at Citrix Synergy (Cisco product integrations)
> 6 - Auto-scaling
> 7 - Host deployment feature
>
> I'd also like to ask that we start proposing new features to the list
> again (I know that some of this has continued, but I think it died
> down a bit). It's going to be important to start thinking about
> timing of our next feature release soon (and to be time bound about
> it), so I think we need to ensure that we're all sharing current
> thoughts, status, etc... And as always, feel free to let me know if
> you disagree!
>
> Thanks all,
>
> -chip
So I'll take silence as meaning that folks are heads down working!
(but I'll start with something from the SunGard team)...
Status of adding Unit Tests:
Yichi started work on a bunch of unit tests for the API project. He
added 100 tests via his patch submissions. They are currently in the
junit-test branch, but there are some issues getting them to run
correctly with Maven (specifically the junit version that is loaded).
Mani is going to be looking at that, and a he and Meghna are going to
be adding more tests to that branch. Once we have the test passing,
I'll merge into master (and hopefully it will jive with the maven
changes going on there).
Also, we're preparing a couple of feature proposals right now, which
we obviously want to get reviewed by the community before proceeding.
Expect them to start showing up in the next week or two.
Looking forward to updates from others!
-chip
Re: Moving beyond 4.0.0-incubating
Posted by Noah Slater <ns...@apache.org>.
Chip,
I think this is a great initiative. Do you have plans for any sort of
roadmap process?
Would be interesting in hearing you thoughts on how we do something like
that.
Thanks,
On 24 October 2012 22:56, Chip Childers <ch...@sungard.com> wrote:
> Hi all,
>
> Obviously we still have to actually pass a vote, and then pass another
> vote within the IPMC, before we can call success with
> 4.0.0-incubating. (And we may have to do this several more times,
> depending on how things go.) However, I think it's time to catch up
> on work that's ongoing, ideas for what to do next, and to start to
> plan out what our next community goals are.
>
> Along those lines, perhaps we can all start communicating a little
> better about where other work stands? I'd like to ask folks that are
> working on features / tools to kick off discussion threads for their
> specific areas. Questions that would be great to have answered
> include: How's the work going generally? Are there any design
> decisions that should be talked about? Any help needed?
>
> Examples that come to mind (in no order, and not exhaustive):
>
> 1- Adding more plugin capabilities to the core design (I assume this
> is what the javelin branch is for)
> 2- RBAC
> 3 - Event handling / message bus integration
> 4 - DevCloud changes
> 5 - Work demonstrated at Citrix Synergy (Cisco product integrations)
> 6 - Auto-scaling
> 7 - Host deployment feature
>
> I'd also like to ask that we start proposing new features to the list
> again (I know that some of this has continued, but I think it died
> down a bit). It's going to be important to start thinking about
> timing of our next feature release soon (and to be time bound about
> it), so I think we need to ensure that we're all sharing current
> thoughts, status, etc... And as always, feel free to let me know if
> you disagree!
>
> Thanks all,
>
> -chip
>
--
NS