Other Cloud Autodiscoveries

Contents

  1. Alibaba Cloud Autodiscovery
    1. Alibaba Discovery Items
  2. DigitalOcean Autodiscovery
    1. DigitalOcean Discovery Items
  3. Linode Autodiscovery
    1. Linode Discovery Items
  4. OpenStack Autodiscovery
    1. OpenStack Discovery Items
  5. Oracle Cloud Autodiscovery
    1. Oracle Cloud Discovery Items

Alibaba Cloud Autodiscovery

Alibaba Discovery Items

Cloud Service/Object Name Where to locate in D42 Accessed API Information Generated
VMs Devices –> All Devices http://ecs-cn-hangzhou.aliyuncs.com Type, name, OS, notes, RAM, CPU, serial number

Click Add Cloud Autodiscovery, and then select Alibaba Cloud as the Cloud Type. Name your job, and then add your Alibaba credentials, including both Access Key ID and your Access Key Secret.

Select one or more Zones for the discovery and select options for Action for Instance not found and Device Name Format. Click Save to add the job to the list of Cloud Autodiscovery jobs. Select the job and click Run Now to run the job immediately or continue editing to schedule runs.

DigitalOcean Autodiscovery

DigitalOcean Discovery Items

Cloud Service/Object Name Where to locate in D42 Accessed API Information Generated
Droplets (VMs) Devices –> All Devices https://api.digitalocean.com Type, name, RAM size, CPU count, HDD Size, Tags, OS, etc.

Click Add Cloud Discovery on the Cloud Discovery page, and then select DigitalOcean as the Cloud Type.

Enter a Token Key, and then select any other options you want for the discovery job.

Click Save and Continue; then you can click Run Now to run the job immediately. Or you can save it and set up a schedule to run the Oracle discovery job.

Linode Autodiscovery

Linode Discovery Items

Cloud Service/Object Name Where to locate in D42 Accessed API Information Generated
VMs Devices –> All Devices https://api.linode.com/v4/linode/instances https://api.linode.com/v4/linode/instances/{linodeId}/disks https://api.linode.com/v4/linode/instances/{linodeId}/ips https://api.linode.com//?api_action=api.spec Name, type, RAM, OS, HDD serial number and size, IP, etc.

For access to Linode, you will need your API Key. To create a Linode API Key, go to your Linode console…

Linode

Select “My Profile” and navigate to “API Keys”

Linode

From here, you can create your API Key that Device42 needs to gain access.

Optionally, you can also:

  • Choose the vendor. Please note that all vendors are user-defined. Device42 does not ship with a list of vendors.
  • Choose a VRF Group. If you select a VRF Group, then all IPs found will be placed in subnets in that VRF Group. This is useful if you have duplicate IPs in your internal network.
  • Check the “Remove unfound instances from Device42″ box. If you check this box, then each time this autodiscovery job is run, any devices that were previously created for this account but were not found by the autodiscovery job will be deleted. By checking this box, you can ensure that Device42 will remain in sync with Linode. If you leave it unchecked, then you may end up with Device42 Cloud Instances (cloud devices) that no longer exist in Linode.

Next, you should “Save and Continue”. Then you can click ‘Run’ to run the job immediately. Or you can save it or save it and have it run on a regular schedule.

OpenStack Autodiscovery

OpenStack Discovery Items

Cloud Service/Object Name Where to locate in D42 Accessed API Information Generated
Hosts Devices –> Unknown Devices v2: /v2.0/tokens 2/v2.0/tenants 3/v2.1/<tenant_id>/os-hypervisors/detail 4/v2.1/<tenant_id>/flavors/detail 5/v2.1/<tenant_id>/servers/detail v3: /v3/auth/tokens 2 /v3/projects Name, memory, CPU count, IP, MAC, etc.
VMs Devices –> All Devices Same as above Type, name, RAM, UUID, IP, MAC, etc.
  1. When you add an OpenStack job, you will be prompted for a User, Password, and Project Name.

Minimum Permission Requirements for OpenStack Discovery are as follows:

  • User / User Group should be attached to the project and have the following permissions described in policy.json:
    • “os_compute_api:os-hypervisors”
    • “os_compute_api:os-extended-server-attributes”
  1. The User and Password are the ones you enter into the Openstack authentication screen…Openstack
  2. When you log into Openstack, the Overview screen shows a list of projects.Openstack
  3. Enter the project name you would like to access into the Device42 Project Name field.

Optionally, you can also:

  • Choose the vendor. Please note that all vendors are user-defined. Device42 does not ship with a list of vendors.
  • Choose a VRF Group. If you select a VRF Group, then all IPs found will be placed in subnets in that VRF Group. This is useful if you have duplicate IPs in your internal network.
  • Check the “Remove unfound instances from Device42″ box. If you check this box, then each time this autodiscovery job is run, any devices that were previously created for this account but were not found by the autodiscovery job will be deleted. By checking this box, you can ensure that Device42 will remain in sync with OpenStack. If you leave it unchecked, then you may end up with Device42 Cloud Instances (cloud devices) that no longer exist in OpenStack.

Next, you can click Save and Continue. Then you can click Run Now to run the job immediately. Or you can save it and set up a schedule to run the discovery job.

Oracle Cloud Autodiscovery

Oracle Cloud Discovery Items

Cloud Service/Object Name Where to locate in D42 Accessed API Information Generated
VMs Devices –> All Devices https://iaas.<<zone>>.oraclecloud.com https://identity.<<zone>>.oraclecloud.com Service name, instance ID, status, location, etc.
Subnets Network –> Subnets https://iaas.<<zone>>.oraclecloud.com https://identity.<<zone>>.oraclecloud.com Network, mask, name

Click Add Cloud Discovery on the Cloud Discovery page, and then select Oracle Cloud as the Cloud Type.

Enter the following information:

  • Name for the discovery job.
  • User ID
  • Fingerprint (if applicable)
  • Key File
  • Tenant ID
  • Zones

You can also:

  • Choose the vendor. Please note that all vendors are user-defined. Device42 does not ship with a list of vendors.
  • Choose a VRF Group. If you select a VRF Group, then all IPs found will be placed in subnets in that VRF Group.
  • Select a Remote Collector.

Scroll down the page to see additional options.

Click Save and Continue; then you can click Run Now to run the job immediately. Or you can save it and set up a schedule to run the Oracle discovery job.


«