Red Hat SummitQuesto contenuto non è disponibile nella lingua selezionata.
13.3. Methods
13.3.1. Creating a New Storage Connection
Copia collegamentoCollegamento copiato negli appunti!
Creating a new storage connection requires a
POST request.
It is possible to create a new storage connection without adding a storage domain. The host
id or name is optional; providing it will attempt a connection to the storage via the host.
Example 13.2. Creating a New Storage Connection
POST /api/storageconnections HTTP/1.1
Accept: application/xml
Content-type: application/xml
<storage_connection>
<type>nfs</type>
<address>domain.example.com</address>
<path>/export/storagedata/username/data</path>
<host>
<name>Host_Name</name>
</host>
</storage_connection>
13.3.2. Deleting a Storage Connection
Copia collegamentoCollegamento copiato negli appunti!
Deleting a storage connection requires a
DELETE request. A storage connection can only be deleted if neither storage domain nor LUN disks reference it.
The host
name or id is optional; providing it unmounts the connection from that host.
Example 13.3. Deleting Storage Connection
DELETE /api/storageconnections/Storage_Connection_ID HTTP/1.1
Accept: application/xml
Content-type: application/xml
<host>
<name>Host_Name</name>
</host>
13.3.3. Updating a Storage Connection
Copia collegamentoCollegamento copiato negli appunti!
Updating an existing storage connection requires a
PUT request. The storage domain must be in either maintenance mode or unattached to successfully update the connection.
Providing the host
name or id is optional; if provided, the host attempts a connection to the updated storage details.
Example 13.4. Updating a Storage Connection
PUT /api/storageconnections/Storage_Connection_ID HTTP/1.1
Accept: application/xml
Content-type: application/xml
<storage_connection>
<address>updated.example.domain.com</address>
<host>
<name>Host_name</name>
</host>
</storage_connection>
13.3.4. Updating an iSCSI Storage Connection
Copia collegamentoCollegamento copiato negli appunti!
Updating an existing iSCSI storage connection requires a
PUT request. An iSCSI storage domain must be in maintenance mode or unattached to successfully update the connection.
Example 13.5. Updating a Storage Connection
PUT /api/storageconnections/Storage_Connection_ID HTTP/1.1
Accept: application/xml
Content-type: application/xml
<storage_connection>
<port>3456</port>
</storage_connection>
13.3.5. Adding New Storage Domain with Existing Storage Connection
Copia collegamentoCollegamento copiato negli appunti!
Adding a new storage domain with existing storage connection requires a
POST request. This is only applicable with file-based storage domains: NFS, POSIX, and local.
Example 13.6. Adding a New Storage Domain with Existing Storage Connection
POST /api/storagedomains HTTP/1.1
Accept: application/xml
Content-type: application/xml
<storage_domain>
<name>New_Domain</name>
<type>data</type>
<storage id="Storage_Connection_ID"/>
<host>
<name>Host_Name</name>
</host>
</storage_domain>
13.3.6. Attaching an Additional Storage Connection to iSCSI Storage
Copia collegamentoCollegamento copiato negli appunti!
Attaching an additional storage connection to an iSCSI storage domain requires a
POST request.
Example 13.7. Attaching an Additional Storage Connection to iSCSI Storage
POST /api/storagedomains/iSCSI_Domain_ID/storageconnections HTTP/1.1
Accept: application/xml
Content-type: application/xml
<storage_connection id="Storage_Connection_ID">
</storage_connection>
13.3.7. Detaching a Storage Connection from iSCSI Storage
Copia collegamentoCollegamento copiato negli appunti!
Detaching a storage connection from an iSCSI storage domain requires a
DELETE request.
Example 13.8. Detaching a Storage Connection from iSCSI Storage
DELETE /api/storagedomains/iSCSI_Domain_ID/storageconnections/Storage_Connection_ID HTTP/1.1
Accept: application/xml
Content-type: application/xml
13.3.8. Defining Credentials to an iSCSI Target
Copia collegamentoCollegamento copiato negli appunti!
When an iSCSI storage domain is added using the Administration Portal, only a single user name and password can be specified for that domain. However, some setups require that each host in the cluster use a separate user name and password. Specific credentials can be applied to each iSCSI target per host by using the
storageconnectionextensions element.
Example 13.9. Defining credentials to an iSCSI target
POST /api/hosts/2ab5e1da-b726-4274-bbf7-0a42b16a0fc3/storageconnectionextensions HTTP/1.1
Accept: application/xml
Content-type: application/xml
<storageconnectionextension>
<target>iqn.2010.05.com.example:iscsi.targetX</target>
<username>jimmy</username>
<password>p@55w0Rd!</password>
</storageconnectionextension>
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}