Sure, Proposal is the right next step. In this email I attached some of recent 
proposals discussed here.

Thanks,
Sergey


On 3/21/17, 10:49 AM, "Shanika Ediriweera" <[email protected]> wrote:

    Hi Sergey,
    
    I went through the guides and the existing drivers Solidfire (
    
https://github.com/apache/cloudstack/tree/master/plugins/storage/volume/solidfire/src/org/apache/cloudstack/storage/datastore)
    and cloudbyte (
    
https://github.com/apache/cloudstack/tree/master/plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore
    ).
    
    Shall I start making my proposal?
    Any advise on it?
    
    Thank you.
    
    Best Regards,
    
    Shanika Ediriweera
    Undergraduate
    Dept. of Computer Science & Eng.
    University of Moratuwa
    
    On 12 March 2017 at 22:12, Sergey Levitskiy <[email protected]>
    wrote:
    
    > Hi Shanika,
    > That’s great. You can start by reviewing Cloudstack development guide
    > https://cloudstack.apache.org/developers.html
    > as well as API and programming resources
    > http://docs.cloudstack.apache.org/en/latest/dev.html
    >
    > ACS source code is here
    > https://git-wip-us.apache.org/repos/asf/cloudstack.git
    > with mirror at https://github.com/apache/cloudstack
    >
    > Some of the design documents available here
    > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Home
    > under Developers->Design
    >
    > Writing a storage driver from scratch will be a huge undertaking so you
    > can consider using one of the existing ones as a prototype e.g. SolidFire
    > or CloudByte.
    >
    > This dev@ mail list is the one you should use if you have questions or
    > wants other people input or opinion.
    >
    > Good luck,
    > Sergey
    >
    >
    >
    >
    >
    

--- Begin Message ---
Hello,

 

I am new to the mailing list, and we are glad to be a part of the CloudStack 
community.  We are looking to develop plugins and modules that will help grow 
and expand the adoption and use of CloudStack.  So as part of my introductory 
email,  I’d like to introduce a little project we have been working on; a 
StorageHA Monitor.  The Monitor would allow CloudStack and the hosts to test, 
communicate and resolve VM availability issues when storage (primary and/or 
secondary) availability becomes apparent.  This is a small write up about how 
it would work:

 

Consists of two scripts/programs:

 

The host script runs on the host servers and checks to see if the primary and 
secondary storage is available by doing a read/write test then reports to the 
master script that runs on the Cloudstack server. The host script will test a 
read  and a write to the storage every 5 seconds (configurable), and if it 
fails 3 times (configurable) then it will be recorded by the master script.

 

The master script will monitor the results of the host script. If the test is 
good, nothing happens and the results are logged and so that we can track the 
history of the test results. If the test reports back as failed, then it will 
perform  the following actions:

 

·        Secondary Storage - It will simply generate and send an alert that the 
failure has occurred.

 

·        Primary Storage - The script will perform the following tasks:

o  Generate and send an alert that the failure has occurred.

o  Force the VMs on that host to shutdown.

o  Determine which host to move the VMs to.

o  Start the VMs on the healthy host.

 

We have already started working on some code, and the solution seems to be 
testing well.  Any thoughts/ideas/input are(is) welcome.  Should there are a 
solution out there already, then please forgive our ignorance, and point us in 
the right  direction. We look forward to further collaboration with you all.

 

Regards,

j

 

Jeromy Grimmett


155 Fleet Street

Portsmouth, NH 03801

Direct: 603.766.3625
Office: 603.766.4908

Fax: 603.766.4729
[email protected]

www.cloudbrix.com

 


--- End Message ---
--- Begin Message ---
All,

I would like propose native functionality into CloudStack to provide a 
container service through which users out-of-the box can use to launch 
container based application. Idea is to support ability to orchestrate the 
resources and automate aspects of setting up container orchestrator through 
CloudStack. Public IAAS service providers AWS with its ECS [1] and google with 
GKE [2] already provides ability container applications.  Competitive cloud 
orchestration platforms already have native support for container service. 
Users of CloudStack both as public cloud providers and users with private 
clouds will benefit with such functionality.

While container orchestrator of user choice can be provisioned on top of 
CloudStack (with out CloudStack being involved) with tools like TerraForm[3], 
Ansible[4] etc, advantage of having native orchestration is giving user a nice 
cohesive integration. This proposal would like add a notion of first class 
CloudStack entity called container cluster which can be used to provision 
resources, scale up, scale down, start and stop the cluster of VM’s on which 
containerised applications can be run. For actual container orchestration we 
will still need container orchestrator like docker swarm, marathon, kubernetes, 
but CloudStack container service can automate setting up of control place 
automatically.

Please see the detailed FS [5], and jira ticket [6]. 

[1]http://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html
[2]https://cloud.google.com/container-engine/
[3] https://github.com/skippbox/ansible-cloudstack
[4]https://github.com/chiradeep/terraform-cloudstack-examples/tree/master/kubernetes-coreos-isolated-nw
[5] 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+container+service+functional+specification+and+design+document
[6]https://issues.apache.org/jira/browse/CLOUDSTACK-9760




--- End Message ---
--- Begin Message ---
All,


I would like to start discussion on a new feature - Host HA for CloudStack.

CloudStack lacks a way to reliably fence a host, the idea of the host-ha 
feature is to provide a general purpose HA framework and HA provider 
implementation specific for hypervisor that can use additional mechanism such 
as OOBM (ipmi based power management) to reliably investigate, recover and 
fence a host. This feature can handle scenarios associated with server crash 
issues and reliable fencing of hosts and HA of VM. The first version will have 
HA provider implementation for KVM (and for simulator to test the framework 
implementation, and write marvin tests that can validate the feature on Travis 
and others).


Please have a look at the FS here:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Host+HA


Looking forward to your comments and questions.


Regards.

[email protected] 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 



--- End Message ---

Reply via email to