2 captures
11 Jun 2018 - 31 Oct 2020
May JUN Jul
11
2017 2018 2019
success
fail

About this capture

COLLECTED BY

Organization: Archive Team

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.

The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.

This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.

Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.

The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.

Collection: Archive Team: The Github Hitrub

This collection is a set of Github repository archives from two major sets: A panic grab upon the acquisition by Microsoft, and a larger, ongoing set of Pretty Much Everything.
TIMESTAMPS

The Wayback Machine - http://web.archive.org/web/20180611010355/https://github.com/openstack-infra/glean
 
Skip to content  





Features  

Business  

Explore  

Marketplace  

Pricing  









Sign in  or Sign up  












Watch  

Star  

Fork  

/glean

 
 






Join GitHub today


GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.

Sign up  






Simple program to write static config from config-drive    







177   commits  

1 branch  

26 releases  

Fetching contributors  

Apache-2.0  




(一) Python  95.6%  

(二) Shell  4.4%  






Python  Shell  





Switch branches/tags  





Branches  

Tags  





master  

Nothing to show
 


1.11.1   1.11.0   1.10.3   1.10.2   1.10.1   1.10.0   1.9.2   1.9.1   1.9.0   1.8.0   1.7.0   1.6.1   1.6.0   1.5.1   1.5.0   1.4.3   1.4.2   1.4.1   1.4.0   1.3.0   1.2.0   1.1.0   1.0.0   0.1.2   0.1.1   0.1.0  

Nothing to show
 






Find file  
Clone or download  



Clone with HTTPS  


Use Git or checkout with SVN using the web URL.  





Download ZIP  


Launching GitHub Desktop...


If nothing happens, download GitHub Desktop and try again.


 

Launching GitHub Desktop...


If nothing happens, download GitHub Desktop and try again.


 

Launching Xcode...


If nothing happens, download Xcode and try again.


 

Launching Visual Studio...


If nothing happens, download the GitHub extension for Visual Studio and try again.


 



Fetching latest commit  

Cannot retrieve the latest commit at this time.  
Permalink  
Failed to load latest commit information.
doc/source
glean
.coveragerc
.gitignore
.gitreview
.mailmap
.testr.conf
CONTRIBUTING.rst
HACKING.rst
LICENSE
MANIFEST.in
README.rst
rebuild-test-output.sh
setup.cfg
setup.py
test-requirements.txt
tox.ini

README.rst  

glean


Glean is a program intended to configure a system based on configuration provided in a configuration drive.

Why would you want glean?


Different cloud providers have different ways of providing networking and other configuration to guest virtual-machines. Many use DHCP but others, notably Rackspace, use configuration provided via a configuration drive.

What does glean do?


Broadly, glean checks for configuration drive based information and, if found, uses that to configure the network. If config-drive is not found, it falls back to configuring any available interfaces with DHCP.

Specifically, it will mount the special block-device with label config-2 and parse the network_info.json and vendor_info.json files within. If appropriate network configuration is found, it will write out network configuration files.

The format of the network_info.json file is documented here. Please note that glean does not implement every feature listed.

If no network info is found there, available interfaces can be probed from /sys/class/net and any that appear to be up will be configured for use with DHCP.

It will also handle authorized_keys and host-name info provided from meta_data.json.

How does glean do this?

systemd environment


glean install will add a udev rules file (99-glean.rules) that triggers on any network device being added. This will run the glean@.service systemd template for the interface specified.

This systemd unit firstly determines if there is already a /etc/sysconfig/network/ configuration for the interface; if so, the interface is considered configured and skipped.

If not, glean is started with the interface specified. The configuration drive is probed to see if network configuration for the interface is available. If so, it will be added, otherwise the interface will configured for DHCP.


Note

glean uses the network init scripts service network.service on RedHat platforms (or the equivalent on other platforms). You should ensure this service is enabled and other tools such as NetworkManager are disabled for correct operation.

How do I use glean?


Glean ships glean-install, a script which install glean into your system startup environment. It should handle sysv, upstart and systemd to cover all major distributions. This should be run once, during install or image build.

The startup environment will be modified as described above to configure any found interfaces.

Differences to cloud-init?


Glean differs to cloud-init mainly in its very reduced dependency footprint. In a dynamic CI environment such as OpenStack, many of the python dependencies for cloud-init can cause conflicts with packages or versions required for testing.

Glean also better supports static IP allocation within config-drive, particuarly important within the Rackspace environment.

More details



Free software: Apache license

Documentation: http://docs.openstack.org/infra/glean

Source: http://git.openstack.org/cgit/openstack-infra/glean

Bugs: http://storyboard.openstack.org

 










© 2018 GitHub, Inc.

Terms

Privacy

Security

Status

Help
 


Contact GitHub

API

Training

Shop

Blog

About
 




You cant perform that action at this time.  

You signed in with another tab or window. Reload to refresh your session.  You signed out in another tab or window. Reload to refresh your session.  

Press h to open a hovercard with more details.