Make the schema more strict for HTTP disks requiring a name and
mandating exactly one source host.
ftp/tftp entries were not moved here, since http transport also will
support cookies and other options, which will be added later.
</element>
</define>
+ <define name="diskSourceNetworkProtocolHTTP">
+ <element name="source">
+ <attribute name="protocol">
+ <choice>
+ <value>http</value>
+ <value>https</value>
+ </choice>
+ </attribute>
+ <attribute name="name"/>
+ <ref name="diskSourceNetworkHost"/>
+ </element>
+ </define>
+
<define name="diskSourceNetworkProtocolGeneric">
<element name="source">
<interleave>
<value>sheepdog</value>
<value>gluster</value>
<value>iscsi</value>
- <value>http</value>
- <value>https</value>
<value>ftp</value>
<value>ftps</value>
<value>tftp</value>
<choice>
<ref name="diskSourceNetworkProtocolGeneric"/>
<ref name="diskSourceNetworkProtocolRBD"/>
+ <ref name="diskSourceNetworkProtocolHTTP"/>
</choice>
</define>