noon
Hello,
We use Artifactory to manage our artifact repository, including syncing our
distro repos from the vendor. Up until now I have been using the import
command to import form a mounted vendor DVD on our Cobbler server. What I
would like to do it is have it always use our Artifactory server as that
will always be available the systems we build. Per documentation the
--available-as option should do this for me. Also, from documentation
examples it shows that it should work over HTTP. The syntax I am using is...
cobbler import --path=http://repo.myserver.com:/artifactory/rhel-6.3-base/x86_64/
--name=rhel6.3 --avaialble-as=http://repo.myserver.com:
/artifactory/rhel-6.3-base/x86_64/
The import task fails. The log shows it tried to use rsync. Does it not
work over http or am I using the wrong syntax?
Mon Nov 5 09:42:30 2012 - INFO | importing from a network location,
running rsync to fetch the files first
Mon Nov 5 09:42:30 2012 - INFO | unsupported protocol
Regards,
Jason
12:25 p.m.
On 11/05/2012 07:00 PM, Jason Graham wrote:
Hello,
We use Artifactory to manage our artifact repository, including syncing
our distro repos from the vendor. Up until now I have been using the
import command to import form a mounted vendor DVD on our Cobbler
server. What I would like to do it is have it always use our Artifactory
server as that will always be available the systems we build. Per
documentation the --available-as option should do this for me. Also,
from documentation examples it shows that it should work over HTTP. The
syntax I am using is...
cobbler import
--path=http://repo.myserver.com:/artifactory/rhel-6.3-base/x86_64/
--name=rhel6.3
--avaialble-as=http://repo.myserver.com:/artifactory/rhel-6.3-base/x86_64/
I haven't played with Cobbler in a a while but 2 thing stand out:
avaialble
shouldn't that be:
available
and
http://repo.myserver.com:/artifactory/rhel-6.3-base/x86_64/
shouldn't that be:
http://repo.myserver.com/artifactory/rhel-6.3-base/x86_64/
Regards,
Patrick
4:54 a.m.
I haven't played with Cobbler in a a while but 2 thing stand out:
avaialble
shouldn't that be:
available
and
http://repo.myserver.com:/artifactory/rhel-6.3-base/x86_64/
shouldn't that be:
http://repo.myserver.com/artifactory/rhel-6.3-base/x86_64/
this works for me where my trees are not available via cobbler - they are populated by
another means
cobbler import --name=CentOS-6.3-x86_64 --path=/export/storage/trees/CentOS-6.3-x86_64
--available-as=http://@@server@@/trees/CentOS-6.3-x86_64
thanks
11 a.m.
I guess I am confused why you have to specify a local path. When I tried it
this it still seems to need the local path. I get that it will use the
"available-as" path when your node is being built. I do not get why it
still needs the local path. Is this so it can grab the pxe images? If that
is the case, would it be better to add the distro and profile manually (not
through the import command) so I only need to copy the pxe images to the
cobbler server?
I want to have as little on the cobbler server as possible.
Regards,
Jason
On Tue, Nov 6, 2012 at 2:54 AM, Tom Brown <tom(a)ng23.net> wrote:
>
> I haven't played with Cobbler in a a while but 2 thing stand out:
>
> avaialble
> shouldn't that be:
> available
>
> and
>
> http://repo.myserver.com:/artifactory/rhel-6.3-base/x86_64/
> shouldn't that be:
> http://repo.myserver.com/artifactory/rhel-6.3-base/x86_64/
>
this works for me where my trees are not available via cobbler - they are
populated by another means
cobbler import --name=CentOS-6.3-x86_64
--path=/export/storage/trees/CentOS-6.3-x86_64 --available-as=http://
@@server@(a)/trees/CentOS-6.3-x86_64
thanks
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
11:23 a.m.
I guess I am confused why you have to specify a local path. When I
tried it this it still seems to need the local path. I get that it will use the
"available-as" path when your node is being built. I do not get why it still
needs the local path. Is this so it can grab the pxe images? If that is the case, would it
be better to add the distro and profile manually (not through the import command) so I
only need to copy the pxe images to the cobbler server?
I want to have as little on the cobbler server as possible.
Yes. The local path is for the kernel and initrd for pxe.
Very little is actually on the cobbler server.
11:32 a.m.
On Mon, Nov 5, 2012 at 12:00 PM, Jason Graham
<jason.michael.graham(a)gmail.com> wrote:
Hello,
We use Artifactory to manage our artifact repository, including syncing our
distro repos from the vendor. Up until now I have been using the import
command to import form a mounted vendor DVD on our Cobbler server. What I
would like to do it is have it always use our Artifactory server as that
will always be available the systems we build. Per documentation the
--available-as option should do this for me. Also, from documentation
examples it shows that it should work over HTTP. The syntax I am using is...
cobbler import
--path=http://repo.myserver.com:/artifactory/rhel-6.3-base/x86_64/
--name=rhel6.3
--avaialble-as=http://repo.myserver.com:/artifactory/rhel-6.3-base/x86_64/
The import task fails. The log shows it tried to use rsync. Does it not work
over http or am I using the wrong syntax?
Mon Nov 5 09:42:30 2012 - INFO | importing from a network location, running
rsync to fetch the files first
Mon Nov 5 09:42:30 2012 - INFO | unsupported protocol
The --path must be local, or it must be an rsync path. HTTP/FTP are
not supported (but work fine in the --available-as part).
4210
days inactive
4211
days old
cobbler@lists.fedorahosted.org
5 comments
4 participants
participants (4)
-
James Cammarata -
Jason Graham -
Patrick Lists -
Tom Brown