| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
|
|
| |
This allows other python applications to import the virtBootstrap
module and call the bootstrap() method.
Example:
>>> import virtBootstrap
>>> virtBootstrap.bootstrap()
|
| | |
|
| |
|
|
|
|
| |
This patch aims to set logger name for the virtBootstrap module.
Set logging format to: %(levelname)s: %(message)s
and use an elegant way of setting log level.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Skopeo does not accept "docker:///" as valid URI format. [1]
However, driver URIs within the Libvirt project and virtualization
tools such as libvirt-sandbox use three slashes after URI scheme. [2]
Make virt-bootstrap auto-correct the source URI for consistency with
other tools.
Following the syntax specifications in RFC 1808, "urlparse" recognizes
a netloc only if it is properly introduced by ‘//’. [3] Otherwise the
input is presumed to be a relative URL and thus to start with a path
component. [4]
- "self.image" is the path component
- "self.registry" is the netloc component
[1] https://github.com/projectatomic/skopeo/blob/master/docs/skopeo.1.md#skopeo-copy-1
[2] http://libvirt.org/uri.html
[3] https://docs.python.org/2/library/urlparse.html
[4] https://hg.python.org/cpython/file/2.7/Lib/urlparse.py#l187
|
| | |
|
| |
|
|
|
|
|
| |
Update logged messages to provide information about the current
state of virt-bootstrap.
E.g "Downloading container image" or "Extracting layer (1/5)"
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Improve readability of logged messages by separating the prefix
from the message with new line and raise CalledProcessError if
the exit code is non-zero.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
These flags aim to control the logging level [1] of virt-bootstrap.
Default = INFO (Confirmation that things are working as expected)
--debug = DEBUG (Detailed information,
typically of interest only when diagnosing problems)
--quiet = WARNING (An indication that something unexpected happened,
or indicative of some problem in the near future)
[1] https://docs.python.org/3/howto/logging.html
|
| |
|
|
|
| |
Log executed commands as well as their stdout/stderr
for easier debugging.
|
| |
|
|
|
|
|
|
| |
To run the code style checks, run `python setup.py pylint`
Only errors could be reported using the option --errors-only.
Could be useful to run in interactive git rebase
Fix the reported pylint errors as well
|
| | |
|
| |
|
|
|
| |
Using the header as mentioned in the GPLv3 text avoids rpmlint
to complain about bad FSF address.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Rename "virt-bootstrap.py" to "virt_bootstrap.py" to avoid installation
issues. Reference: https://stackoverflow.com/a/30284007
Install:
$ sudo ./setup.py install
Clean:
$ sudo ./setup.py clean --all
Uninstall:
$ sudo pip uninstall virt-bootstrap
Or:
$ sudo ./setup.py install --record installed_files.txt
$ cat installed_files.txt | xargs sudo rm -rf
|
| |
|
|
|
|
|
|
| |
When python is not /usr/bin/python but something else that is still
found by your system, /usr/bin/env still finds it.
:x
Reference:
https://mail.python.org/pipermail/python-list/2012-September/631967.html
|
|
|
Preparatory commit before setup.py introduction.
|
