I made a few options available such as Azure location, storage
account, role, etc…
The README contains screenshots, and a brief tutorial on how to
configure it. You will need to store the management certificate on the
Foreman server so it can have the appropriate Azure credentials.
The plugin is published on the 1.11 and 1.12 repositories, and it's
packaged as rpm (tfm-rubygem-foreman_azure) and deb (rubygem-foreman_azure).
Please try it out and let us know what you think, what's missing, bugs,
etc… Patches are highly welcome
I made a few options available such as Azure location, storage
account, role, etc…
The README contains screenshots, and a brief tutorial on how to
configure it. You will need to store the management certificate on the
Foreman server so it can have the appropriate Azure credentials.
The plugin is published on the 1.11 and 1.12 repositories, and it’s
packaged as rpm (tfm-rubygem-foreman_azure) and deb
(rubygem-foreman_azure).
Please try it out and let us know what you think, what’s missing, bugs,
etc… Patches are highly welcome
···
On 15/06/16 12:09, Daniel Lobato Garcia wrote:
> The plugin is published on the 1.11 and 1.12 repositories, and it's
> packaged as rpm (tfm-rubygem-foreman_azure) and deb (rubygem-foreman_azure).
I'm starting to play with and test foreman_azure and have a few questions:
First, I see that importing the certificate into Azure requires use of the
'classic' portal and only 'classic' style VM's in Azure are visible through
Foreman. Is this expected? Should I be able to see all VM's (both classic
and non-classic) in Foreman?
Secondly, I'm a bit confused on the provisioning/finish/user_data template
options since I do not have any prior experience using image/cloud based
deployments in Foreman. What type of template should I use to install
Puppet and do other 'post-image install' type stuff? Should I be using
user-data/cloud-init with Azure or do I need to just a more generic
template that simply uses SSH to execute these types of things?
Thanks again,
Josh
···
On Wed, Jun 15, 2016 at 7:09 AM, Daniel Lobato Garcia wrote:
Hi Foreman users!
A while ago we made a survey about whether you would prefer to see
Hyper-V or Azure support on Foreman, and Azure won the survey.
I made a few options available such as Azure location, storage
account, role, etc…
The README contains screenshots, and a brief tutorial on how to
configure it. You will need to store the management certificate on the
Foreman server so it can have the appropriate Azure credentials.
The plugin is published on the 1.11 and 1.12 repositories, and it’s
packaged as rpm (tfm-rubygem-foreman_azure) and deb
(rubygem-foreman_azure).
Please try it out and let us know what you think, what’s missing, bugs,
etc… Patches are highly welcome
> Hi Daniel,
>
> I'm starting to play with and test foreman_azure and have a few questions:
>
> First, I see that importing the certificate into Azure requires use of the
> 'classic' portal and only 'classic' style VM's in Azure are visible through
> Foreman. Is this expected? Should I be able to see all VM's (both classic
> and non-classic) in Foreman?
I think only 'classic' style VMs are supported through their API, if you
find a way to create both (ideally through fog-azure), I'd be glad to
implement it.
> Secondly, I'm a bit confused on the provisioning/finish/user_data template
> options since I do not have any prior experience using image/cloud based
> deployments in Foreman. What type of template should I use to install
> Puppet and do other 'post-image install' type stuff? Should I be using
> user-data/cloud-init with Azure or do I need to just a more generic
> template that simply uses SSH to execute these types of things?
user-data would be the best, as that doesn't require your VMs to have a
public IP (IIRC user-data is sent to the compute resource in question,
in this case Azure, and runs automatically after provision).
In any case if you have public IPs, SSH is fine too. I'd recommend
deploying a smart-proxy box in Azure so then you can serve templates
through it.
> Thanks again,
No problem! Let us know how it goes, and if you find anything that we
have not documented properly, please send some patches to the README
-our little manual for this plugin since it's so small-
···
On 06/16, Josh Baird wrote:
Josh
On Wed, Jun 15, 2016 at 7:09 AM, Daniel Lobato Garcia elobatocs@gmail.com > wrote:
Hi Foreman users!
A while ago we made a survey about whether you would prefer to see
Hyper-V or Azure support on Foreman, and Azure won the survey.
I made a few options available such as Azure location, storage
account, role, etc…
The README contains screenshots, and a brief tutorial on how to
configure it. You will need to store the management certificate on the
Foreman server so it can have the appropriate Azure credentials.
The plugin is published on the 1.11 and 1.12 repositories, and it’s
packaged as rpm (tfm-rubygem-foreman_azure) and deb
(rubygem-foreman_azure).
Please try it out and let us know what you think, what’s missing, bugs,
etc… Patches are highly welcome
> > Hi Daniel,
> >
> > I'm starting to play with and test foreman_azure and have a few questions:
> >
> > First, I see that importing the certificate into Azure requires use of the
> > 'classic' portal and only 'classic' style VM's in Azure are visible through
> > Foreman. Is this expected? Should I be able to see all VM's (both classic
> > and non-classic) in Foreman?
>
> I think only 'classic' style VMs are supported through their API, if you
> find a way to create both (ideally through fog-azure), I'd be glad to
> implement it.
>
> > Secondly, I'm a bit confused on the provisioning/finish/user_data template
> > options since I do not have any prior experience using image/cloud based
> > deployments in Foreman. What type of template should I use to install
> > Puppet and do other 'post-image install' type stuff? Should I be using
> > user-data/cloud-init with Azure or do I need to just a more generic
> > template that simply uses SSH to execute these types of things?
>
> user-data would be the best, as that doesn't require your VMs to have a
> public IP (IIRC user-data is sent to the compute resource in question,
> in this case Azure, and runs automatically after provision).
Actually let me eat my words, user-data is not supported in the azure
compute resource, I just saw
it's not even an attribute of the API. Deploying a smart-proxy in that
network (or Foreman itself) to serve the finish templates would be the
way to go here
···
On 07/08, Daniel Lobato Garcia wrote:
> On 06/16, Josh Baird wrote:
In any case if you have public IPs, SSH is fine too. I’d recommend
deploying a smart-proxy box in Azure so then you can serve templates
through it.
Thanks again,
No problem! Let us know how it goes, and if you find anything that we
have not documented properly, please send some patches to the README
-our little manual for this plugin since it’s so small-
Josh
On Wed, Jun 15, 2016 at 7:09 AM, Daniel Lobato Garcia elobatocs@gmail.com > > wrote:
Hi Foreman users!
A while ago we made a survey about whether you would prefer to see
Hyper-V or Azure support on Foreman, and Azure won the survey.
I made a few options available such as Azure location, storage
account, role, etc…
The README contains screenshots, and a brief tutorial on how to
configure it. You will need to store the management certificate on the
Foreman server so it can have the appropriate Azure credentials.
The plugin is published on the 1.11 and 1.12 repositories, and it’s
packaged as rpm (tfm-rubygem-foreman_azure) and deb
(rubygem-foreman_azure).
Please try it out and let us know what you think, what’s missing, bugs,
etc… Patches are highly welcome
