Content Comparison

...

3. Deploy application with new .ebextension config.

eb deploy

SCCM

To install Breeze Agent via SCCM, we recommend using PowerShell script that will download the agent installer to a target machine and install it.

Download the Breeze Agent installer to any location where it can be downloaded by the target machine. In our example, we will use a shared folder with permission for account that set as Client Push Installation account for SCCM Site.

1. Create a new script in Software Library using the sample below.

2. Change the $url variable to your Breeze Agent installer location.

3. Make sure that target systems have access to the installer’s location.

4. Run the script on system or group to install Breeze Agent.

Script sample:

function New-TemporaryDirectory {
  $parent = [System.IO.Path]::GetTempPath()
  [string]$name = [System.Guid]::NewGuid()
  New-Item -ItemType Directory -Path (Join-Path $parent $name)
}

$url = "\\10.0.0.69\d\breeze-agent.exe"
$tmp_dir = New-TemporaryDirectory
$agent_sfx = "$tmp_dir\breeze-agent.exe"

# download agent installer
(New-Object System.Net.WebClient).DownloadFile($url, $agent_sfx)

# install agent
Start-Process $agent_sfx -ArgumentList '-gm2' -NoNewWindow -Wait

# clean up
Remove-Item "$tmp_dir" -recurse

AWS EC2 User Data script

You can install Breeze agent on AWS EC2 instance's using 'EC2 instance user data' during the initial launch of the instance. The script involves the following steps:

...

Upload the Breeze installer file(s) to AWS S3 Bucket1.

1. Download Breeze Agent installers from Cloudaware CMDB.

...

1. Upload them to the S3 Bucket.

Generate a Presigned object URL for each installer

...

Default lifetime for this URL is 1 hour (or 3600 seconds). You can manually define the URL lifetime by adding -

• -expires-in <time in seconds>

option:

~$ aws s3 presign s3://breeze-agents/breeze-agent.linux.tgz --expires-in 300

...

SCCM

To install Breeze Agent via SCCM, we recommend using PowerShell script that will download the agent installer to a target machine and install it.

Download the Breeze Agent installer to any location where it can be downloaded by the target machine. In our example, we will use a shared folder with permission for account that set as Client Push Installation account for SCCM Site.

1. Create a new script in Software Library using the sample below.

2. Change the $url variable to your Breeze Agent installer location.

3. Make sure that target systems have access to the installer’s location.

4. Run the script on system or group to install Breeze Agent.

Script sample:

function New-TemporaryDirectory {
  $parent = [System.IO.Path]::GetTempPath()
  [string]$name = [System.Guid]::NewGuid()
  New-Item -ItemType Directory -Path (Join-Path $parent $name)
}

$url = "\\10.0.0.69\d\breeze-agent.exe"
$tmp_dir = New-TemporaryDirectory
$agent_sfx = "$tmp_dir\breeze-agent.exe"

# download agent installer
(New-Object System.Net.WebClient).DownloadFile($url, $agent_sfx)

# install agent
Start-Process $agent_sfx -ArgumentList '-gm2' -NoNewWindow -Wait

# clean up
Remove-Item "$tmp_dir" -recurse

Chef

1. Clone the public-utilities repo to your server:

git clone https://github.com/cloudaware/public-utilities.git

2. Put your Breeze Agent installer files to the public-utilities/chef-modules/breeze-agent/files directory. Ensure the files are named breeze-agent-linux.tgz and breeze-agent-windows.exe.

3. Copy Breeze Agent cookbook to your cookbook directory and upload it to the server:

cp -r public-utilities/chef-modules/breeze-agent ~/cookbooks/
knife cookbook upload breeze-agent

4. Create the breeze-agent role:

export EDITOR=vim #any other editor can be selected, like nano for instance
knife role create breeze-agent

Once in the editor, replace everything with the following and save:

{
  "name": "breeze-agent",
  "description": "",
  "json_class": "Chef::Role",
  "default_attributes": {},
  "override_attributes": {},
  "chef_type": "role",
  "run_list": [ "recipe[breeze-agent]" ],
  "env_run_lists": {}
}

5. Add the role to the nodes that you need or to all nodes using your web interface or the folowing command:

knife node run_list add $NODE_NAME 'role[breeze-agent]' #Where $NODE_NAME is the name of the actual node

To add the role to all nodes, run:

for node in `knife node list`;do knife node run_list add $node 'role[breeze-agent]';done;

Next chef-client will apply the changes on the nodes. Please note that it may take some time.

Puppet

1. Put Puppet module breeze_agent to the /etc/puppetlabs/code/environments/production/modules/.

2. Put Breeze Agent installer files to the /etc/puppetlabs/code/environments/production/modules/breeze_agent/files directory.

3. Attach breeze_agent class to the necessary group in the Puppet Dashboard.

4. Add the required variables breeze_package_linux and breeze_package_windows.

Ansible

1. Put Breeze Agent installer files to the 'files' directory.

2. Specify the installer file name and hosts in breeze_agent_linux.yml and breeze_agent_windows.yml

- hosts: linux
  vars:
    linux_agent: linux-breeze-agent.tgz

Proxy support

To add the proxy support to Breeze agent, you need to edit the startup script.

...