commit b2dc64039e812dc0a7f89919a10eb861fc41daae
Author: Pete Zaitcev <zaitcev(a)kotori.zaitcev.us>
Date: Wed Jul 6 17:04:05 2011 -0600
doc: update comments
We supported SSL in RHEV-M URLs since the addition of RHEV-M 2.2, which
almost always comes with SSL and nothing else. So, delete the comment.
Also, we have docs.
backend.c | 6 +-----
1 files changed, 1 insertions(+), 5 deletions(-)
---
diff --git a/backend.c b/backend.c
index 163f1e8..cd1a685 100644
--- a/backend.c
+++ b/backend.c
@@ -1465,10 +1465,6 @@ fs_rhevm_register (my_state *ms, const provider_t *prov, const char
*next,
}
#endif
- /*
- * This is always "http://xxxxxx.xxxx.xxx/rhevm-api".
- * SSL does not work yet, sorry.
- */
api_url = kv_hash_lookup(args,"api-url");
if (!api_url) {
/* TBD: This has to have a defined field in provider, too. */
@@ -1495,7 +1491,7 @@ fs_rhevm_register (my_state *ms, const provider_t *prov, const char
*next,
}
/*
- * We need to document how this all works.
+ * Details are in doc/registrations.md, but here's the gist:
* - NFS host and NFS path are matched against the list of storage
* domains in RHEV-M (we fetch the list using RESTful API).
* This way we find the UUIDs that we have to write out.
Show replies by thread