Hi Sathyasuriya,

On Wed, Jul 23, 2014 at 12:52 AM, Sathyasuriya Priya
<sathyasur...@gmail.com> wrote:
> Thanks Udara & Nirmal.
>
> Could you pls point to any doc/wiki on configuring generic cartridge.
> It should at least have pupper client installed & configured to point to
> puppet master IP, so that other packages can be installed.
> Should I install these manually and create an image out of it, and that is
> called generic cartridge ?

Yes, you can use the config.sh script under
<source_home>/tools/puppet3-agent directory to create a generic
cartridge. But you do not need to point to Puppet master IP since
init.sh script will automatically handle that at the instance start
up. All the cartridge instances will receive its Puppet master IP and
master hostname via payload user-data.

This is explained in Wiki in [1]

>
> I was thinking cartridge json [1] will have some setting (under the
> deployment tree, in below json) to point to puppet client install scripts,
> puppetmaster IP, etc, so that jclouds can directly install them
> automatically ?
> Is that not the case ?

JClouds cannot directory install packages into launched instances. We
have use some configuration management tool like Puppet to do that.
You have to specify the Puppet master IP and domain when installing
Stratos. This information will be kept in cloud controller and passed
to every launched cartridge instance. Cartridge instances will execute
init.sh script at start up, which will configure them selves to point
to Puppet master and receive the relevant configuration depending on
the cartridge service name.

Basically when you run config.sh script, it will install Puppet agent
and copy the init.sh (in <source_home>/tools/puppet3-agent) to
/root/bin/ and add a new entry in /etc/rc.local so that it will get
executed at the start up.


[1] 
https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Creating+a+Cartridge+on+EC2


Thanks.


>
> "deployment": {},
> "iaasProvider": [
>     {
>       "type": "openstack",
>
>
>
> [1]
> https://github.com/suriyapriya/stratos-vagrant-box/blob/master/tests/example_cartridge.json
>
> Thanks
> Suriya
>
>
> On Tue, Jul 22, 2014 at 2:02 AM, Nirmal Fernando <nirmal070...@gmail.com>
> wrote:
>>
>> Hi Suriya,
>>
>> You can go ahead with the generic cartridge image. It'll be the easiest.
>>
>>
>> On Tue, Jul 22, 2014 at 1:18 PM, Sathyasuriya Priya
>> <sathyasur...@gmail.com> wrote:
>>>
>>> hi Nirmal, Devs,
>>>
>>> I am able to configure partition, autoscale, deployment policy, deploy
>>> cartridge, and subscribe to cartridge as well.
>>>
>>> A VM instance gets created in GCE during the subscribe step as well.
>>>
>>> TID: [0] [STRATOS] [2014-07-21 06:37:24,203]  INFO
>>> {org.apache.stratos.cloud.controller.impl.CloudControllerServiceImpl} -
>>> Instance is successfully starting up. MemberContext
>>> [memberId=php111.php.domain2cd18188-2a20-41b4-bdd2-72c9c2e08119,
>>> nodeId=asia-east1-b/php111php-1ff, clusterId=php111.php.domain,
>>> cartridgeType=php, privateIpAddress=null, publicIpAddress=null,
>>> allocatedIpAddress=null, initTime=1405924588145, lbClusterId=null,
>>> networkPartitionId=G1]
>>> {org.apache.stratos.cloud.controller.impl.CloudControllerServiceImpl}
>>>
>>> I had some clarification on cartridge image creation. I see there are 2
>>> ways [1].
>>> Does the "generic cartridge" method supported as well ?
>>> Could you pls confirm what method EC2, openstack, vCloud use [2] ?
>>> To me it looks like "fully configured cartridge" is used for those ?
>>>
>>> [1]
>>> https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Cartridge#id-4.0.0Cartridge-Genericcartridge
>>> [2]
>>> https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Creating+a+Cartridge
>>>
>>> Thanks
>>> Suriya
>>
>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>
>



-- 
Akila Ravihansa Perera
Software Engineer
WSO2 Inc.
http://wso2.com

Phone: +94 77 64 154 38
Blog: http://ravihansa3000.blogspot.com

Reply via email to