Hi,
We recently introduced a facter named "platform" to denote a PaaS framework
or cluster management system on which WSO2 products could be deployed. With
this addition I feel there is no reason to keep - "vm_type/%{::vm_type}"
hierarchy. Also we need to way to introduce configuration parameters
+1
How about wso2/kubernetes.yaml instead of wso2/kubernetes/common.yaml? Will
there be a YAML file in addition to the common.yaml?
- "wso2/%{::platform}"
Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
Hi Chamila,
Agreed. I don't think there would be anymore files in addition to
common.yaml here. How about moving this to root level; for eg:
"platform/kubernetes.yaml" ?
Full Hierarchy will be as follows;
:hierarchy:
- "node/%{::clientcert}"
-
"wso2/%{::product_name}/%{::product_version
+1, IMO that's better since now it's clear how what kubernetes.yaml stands
for.
Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Mon, May 9, 2016 at 12:21 PM, Akila Ravihansa Perera
wrote:
> Hi Chamil
Hi,
It seems "vm_type" hierarchy should exist to build Docker images
(provisioned via Puppet) and then run on bare Docker. Because when building
the images for default platform (which is the option for bare Docker),
there should be a separate hierarchy to set the installation_dir parameter
to "/mn
Hi Akila,
Why don't we use Docker as a platform rather than a vm_type? I'm not sure
about Rocket, however if there are no considerable data duplication between
Docker and a possible Rocket configuration data set, IMO we should keep the
hierarchy simple and include Docker as a platform. WDYT?
Reg
Hi Chamila,
Docker is not really a platform if you look at the semantics. If we create
another YAML for docker under platform hierarchy then we have to duplicate
every platform specific YAML files under product hierarchy. I don't think
it's a good option for us.
Thanks.
On Tue, May 10, 2016 at 6
I agree. Let's keep vm_type for simplicity.
Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Tue, May 10, 2016 at 6:15 AM, Akila Ravihansa Perera
wrote:
> Hi Chamila,
>
> Docker is not really a platfo
Say I want to use in docker-compose (with pure docker). What hiera files
(config) I have to use?
On Tue, May 10, 2016 at 6:18 AM, Chamila De Alwis wrote:
> I agree. Let's keep vm_type for simplicity.
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Software Enginee
Hi Lakmal,
Hierarchy will be the same (hiera.yaml). You need to set docker-compose
specific configuration in "vm_type/docker-compose.yaml" file. This is for
when building the image. Puppet cannot handle run time configuration in
container scenario. If there is no platform (Mesos, K8s etc.) involve
Say platform k8s , we need to have vm_type right? I want to use vm_type
docker , but without any platform configuration. How can I do that?
On Tue, May 10, 2016 at 9:51 AM, Akila Ravihansa Perera
wrote:
> Hi Lakmal,
>
> Hierarchy will be the same (hiera.yaml). You need to set docker-compose
> sp
You do not have to add config data for each hierarchy. If you want to use
without any platform configuration then you can set the "platform" facter
variable to "default".
On Tue, May 10, 2016 at 9:54 AM, Lakmal Warusawithana
wrote:
> Say platform k8s , we need to have vm_type right? I want to us
12 matches
Mail list logo
