- openstack-discuss - lists.openstack.org

[all][tc] OpenStack 2024.2 testing runtime
by Ghanshyam Mann 12 Feb '24

12 Feb '24

Hi All, Its time to deifne the testing runtime for next cycle 2024.2. I have proposed it in gerrit, feel free to review/feedback there. - https://review.opendev.org/c/openstack/governance/+/908862 Changes from previous cycle testing runtime for quick ref: * Removing python 3.8 support because it is EOLing in oct 2024[1] which means python 3.9 will be the minimum python version in testing runtime. * Remove Debian 11 from Additional testing support because 2024.2 is non-SLURP release and previous SLURP release 2024.1 supported Debian 12 also which is what can be used as smooth upgrade to future SLURP release 2025.1 * Removing Nodejs from runtime: Nodejs is not a runtime requirement for Horizon instead it is one of the test dependency. It does not fit as a runtime and can be handle by Horizon team based. Added Horizon team to review this change. -gmann

1 0

[neutron][vpnaas][ovn] Pushing VPNaaS support through OVN
by Mohammed Naser 12 Feb '24

12 Feb '24

Hi all! One of the biggest show stoppers for us for OVN is VPNaaS but I think it’s time that we’d like to be involved in getting it over the line, I want to thank Bodo who has shown a lot of patience in getting the code necessary, and it seems that the code works for them in production as well. I’d like to ask if possible for folks to review these two outstanding changes: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/847007 https://review.opendev.org/c/openstack/neutron-vpnaas/+/765353 I know Slawek had some concerns, so hoping that raising via the email list if Bodo can address those and over the next bit of time we can get this landed in, since it even has actual proper testing both in CI and with user feedback. Thanks! Mohammed

6 8

[neutron] Bugs deputy report February 5th to 11th
by Rodolfo Alonso Hernandez 12 Feb '24

12 Feb '24

Hello all: This is the bug list from the past week: Critical ======================== https://bugs.launchpad.net/neutron/+bug/2052509. "[CI][ovs/ovn sqlalchemy master] jobs broken with Exception: Not enough arguments given". Assigned. Patch: https://review.opendev.org/c/openstack/devstack/+/908572 https://bugs.launchpad.net/neutron/+bug/2052787. "SSH timeouts due to problems with metadata server in ML2/OVN backend". Assigned. High ======================== https://bugs.launchpad.net/neutron/+bug/2052628. "[stable-only][ovn-octavia-provider] Multiple listener-pool-member on IPv6 LB getting second pool in ERROR". Assigned. Patch: https://review.opendev.org/q/I37e660d5eaa45deb38ff127cf69195b0a9ef0846 (merged). Medium ======================== https://bugs.launchpad.net/neutron/+bug/2052484. "[DEFAULT] rpc_worker=0 leaves one rpc worker". Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/908173 https://bugs.launchpad.net/neutron/+bug/2052681. " Many stale neutron-keepalived-state-change processes left after upgrade to native pyroute2 state-change". Not assigned. https://bugs.launchpad.net/neutron/+bug/2052821. "[OVN] Pin a Logical_Router to a chassis when the external network is tunnelled". Assigned. https://bugs.launchpad.net/neutron/+bug/2052843. "[OVN Octavia Provider] subnet with multiple router gateways lb association". Assigned. Patch: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/908679 https://bugs.launchpad.net/neutron/+bug/2052419. "SG list retrieval is slow because we are always loading "synthetic_fields"". Assigned. Patches: https://review.opendev.org/q/I300464472f2348d148f2a3ddac384c883d9d815b Low ======================== https://bugs.launchpad.net/neutron/+bug/2052508. " [doc][troubleshooting] how to enable ovs vswitchd debug logs". Not assigned. https://bugs.launchpad.net/neutron/+bug/2052786. " Add "socket" to NUMA affinity policy". Assigned. Patch: https://review.opendev.org/c/openstack/neutron-lib/+/903531 Regards.

1 0

PTG April 2024 Team Signup Deadline Approaching!
by Kendall Nelson 11 Feb '24

11 Feb '24

Hello Everyone, This is your *last call *to sign up your team up for the next Project Teams Gathering (PTG)[1], which will be held from Monday, April 8 to Friday, April 12 2024! If you haven't already done so and your team is interested in participating, *you need to complete the survey[2] by February 18, 2024 at 7:00 UTC*. Thanks! -Kendall Nelson (diablo_rojo) [1] PTG Site: https://openinfra.dev/ptg/ [2] Team Survey: https://openinfrafoundation.formstack.com/forms/april2024_ptg_survey

1 0

[openstack-ansible] [kolla-ansible] 2023.1 Antelope - In series upgrade - All/few neutron agents dead
by Shrishail K 11 Feb '24

11 Feb '24

Hi Team, I would like to seek some help regarding the issue I am facing while performing in series upgrade on the Antelope version. We have currently deployed our cluster with *2023.1 Antelope *version. The cluster was deployed on a clean environment by cleaning up any previous kolla openstack installation. We have not observed any issues with this environment so far. For a feature I am working on, I had to *put a patch into GLANCE image* and rebuild all *kolla images with a new tag*. I have attempted to upgrade the cluster using both *kolla-deploy *and *kolla-upgrade *methods, but both methods have left the *cluster in degraded condition*. The issue seems to be mainly with failure of communication between *neutron-server *and all/some *neutron-agents, *due to which the neutron-server sees *all/some* *neutron-agents dead*. *Rabbitmq *itself seems to be doing fine. The issue is very consistent. Is this a known behavior? And am I using the correct kolla tools to perform the in series upgrade. Appreciate any help. Thanks, Shrishail

1 0

OpenSUSE packages
by Kai Jellinghaus 11 Feb '24

11 Feb '24

Hello, I hope it's OK to ask a question like this here, not totally sure how else to reach someone knowledgeable from the community. I'm playing with OpenStack on OpenSUSE, but I'm a bit confused where to get the latest packages. From what I can tell 2023.2 is the latest (non-dev) version, sometimes also called "Bobcat", but the website only lists it as 2023.2, so I'm guessing codenames have been discontinued? This page: https://docs.openstack.org/install-guide/environment-packages-obs.html only goes up to Ussuri Browsing OBS I can find builds & repos for > Ussuri, but it seems builds are largely broken. I'd appreciate any help here, I'm not that experienced with OpenStack, OpenSUSE or mailinglists, so I hope I'm not doing/asking for something stupid. Please do point it out if I do, thank you! Kind Regards, Kai Jellinghaus

2 2

haproxy running configuration change openstack-ansible (ussuri)
by keshav bareja 10 Feb '24

10 Feb '24

Hi All I need to change haproxy configuration in the openstack-ussuri environment using openstack-ansible. for glance-api service I need to change backend load-balancing algorithm from source to least-connect I can see this configuration as part of group_vars of the source package* /opt/openstack-ansible <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/inventory <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/group_vars <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/haproxy <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/haproxy.yml* -service: haproxy_service_name: glance_api haproxy_backend_nodes: "{{ groups['glance_api'] | default([]) }}" haproxy_ssl: "{{ haproxy_ssl }}" haproxy_port: 9292 *haproxy_balance_alg: source* haproxy_balance_type: http haproxy_backend_options: Can you please let me know how to do so?

2 3

Re: Welcome to the "openstack-discuss" mailing list
by keshav bareja 09 Feb '24

09 Feb '24

Hi All I need to change haproxy configuration in the openstack-ussuri environment using openstack-ansible. for glance-api service I need to change backend load-balancing algorithm from source to least-connect I can see this configuration as part of group_vars of the source package* /opt/openstack-ansible <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/inventory <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/group_vars <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/haproxy <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/haproxy.yml* -service: haproxy_service_name: glance_api haproxy_backend_nodes: "{{ groups['glance_api'] | default([]) }}" haproxy_ssl: "{{ haproxy_ssl }}" haproxy_port: 9292 *haproxy_balance_alg: source* haproxy_balance_type: http haproxy_backend_options: Can you please let me know how to do so? Regards Keshav On Fri, Feb 9, 2024 at 8:27 PM < openstack-discuss-request(a)lists.openstack.org> wrote: > Welcome to the "openstack-discuss" mailing list! > > To post to this list, send your message to: > > openstack-discuss(a)lists.openstack.org > > You can unsubscribe or make adjustments to your options via email by > sending a message to: > > openstack-discuss-request(a)lists.openstack.org > > with the word 'help' in the subject or body (don't include the > quotes), and you will get back a message with instructions. You will > need your password to change your options, but for security purposes, > this password is not included here. If you have forgotten your > password you will need to reset it via the web UI. >

2 1

[release] Release countdown for week R-7
by Thierry Carrez 09 Feb '24

09 Feb '24

Development Focus ----------------- We are entering the last weeks of the 2024.1 Caracal development cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-AC freeze, in preparation for elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Contributor and allowed to vote. This is done by adding extra-acs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-AC freeze on February 15, 2024. A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * Oslo libraries are entering feature freeze next week, February 15, 2024. * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (February 22, 2024). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 29, 2024) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 29, 2024. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (March 15, 2024) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (March 29, 2024) Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to one week after Feature freeze (March 7, 2024). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… jeremy [at] openstack.org/fungi on IRC is available if you need help selecting or writing your highlights. Upcoming Deadlines & Dates -------------------------- Extra-AC freeze: February 15, 2024 (R-7 week) Oslo feature freeze: February 15, 2024 (R-7 week) Non-client library freeze: February 22, 2024 (R-6 week) Client library freeze: February 29, 2024 (R-5 week) caracal-3 milestone: February 29, 2024 (R-5 week) Cycle highlights deadline: March 7, 2024 (R-4 week) Dalmatian PTG: April 8-12, 2024 -- Thierry Carrez (ttx)

1 0

[Neutron][OVN] Flat routed provider network has external traffic broadcasted to all VMs
by Daniel Failing 09 Feb '24

09 Feb '24

Dear all, I'm currently debugging a (testing) deployment with neutron/OVN, currently most ports in external flat network. So far I'm happy everything can communicate, but we see a strong performance degradation with increasing number of VMs/ports hosted on a hypervisor. The setup is similar to the one described in the routed provider networks docs [1]. For routing between the different segments, we have physical routers, that are not managed by neutron. Debugging the issue showed traffic originating from the DC router to VMs go perfectly as unicast traffic through OVN. Communicating from the VM to other networks via the DC router, however, will broadcast the traffic to all attached ports on the internal bridge. Is there a way to tell neutron/OVN to use a specific MAC address for the router and forward the traffic through the patch port instead of broadcasting it? I could not find any documentation of whether I am missing a neutron port or some other configuration on the hypervisor. Just to make sure: The VM and DC routers have the right ARP information of itself, the traffic that is duplicated is from VM to router/external network. (via default route to router) As far as I could see, this issue does not appear with private networks, since all MAC addresses are known to OVN/Neutron. Versions: Nova/Neutron: Yoga ovs-vswitchd (Open vSwitch) 3.1.4 ovn-northd 22.12.1 kernel 5.14.0-284.30.1.el9_2.x86_64 Best, Daniel [1] https://docs.openstack.org/neutron/latest/admin/config-routed-networks.html

2 4

[manila] multi az replication
by garcetto 08 Feb '24

08 Feb '24

good afternoon, i am using zed, on streched ceph as backend on multiple az. i would like to emulate aws efs multiple nfs mount points for each user tenant (one on each different az) using manila, is it possible? ideally i would like to expose to each users tenant a manila vm as nfs exporter to custormer' instances, and as backend (of manila) use a cinder volume on ceph (rbd? cephfs? nfs?) my problem is how can i create say 3 different manila service vms (one in each az) with different frontend ips all pointing to same rbd/cephfs volume? am i doing wrong? thank you.

2 1

[neutron] Drivers meeting cancelled tomorrow
by Brian Haley 08 Feb '24

08 Feb '24

Hello Neutrinos: Due to the lack of agenda, Friday's drivers meeting is cancelled. Have a nice weekend! -Brian

1 0

[kolla] [Ironic] Is ironic_cleaning_network is tenant network?
by Jayesh Chaudhari 08 Feb '24

08 Feb '24

Hi, I am trying to implement Ironic in my kolla-ansible yoga setup. I am following below document https://docs.openstack.org/kolla-ansible/yoga/reference/bare-metal/ironic-g… Here in ironic_cleaning_network and dnsmasq_dhcp_range is from tenant network?

2 1

[manila] share replication still experimental?
by garcetto 08 Feb '24

08 Feb '24

good evening, is still experimental even in zed or later? https://docs.openstack.org/manila/latest/admin/shared-file-systems-share-re… thank you.

2 1

[magnum] Is magnum support region_name in keystone auth config?
by Seongsoo Cho 08 Feb '24

08 Feb '24

Hi magnum team. It seems that a magnum does not support region_name which is in the keystone_auth and keystone_authtoken section in magnum conf. The internal keystone client of keystoneauth1 only uses the lowest UUID of endpoints for keystone url. [1] And also KeystoneClientV3 's get_auth[2] and get_legacy_auth[3] also don't support region_name as an argument. So, My question is how can I make magnum only use the keystone URL written in the config? Best regards Seongsoo Cho [1] https://github.com/openstack/keystoneauth/blob/master/keystoneauth1/access/… [2] https://github.com/openstack/magnum/blob/master/magnum/common/keystone.py#L… [3] https://github.com/openstack/magnum/blob/master/magnum/common/keystone.py#L… -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

2 2

about magnum capi for production
by Nguyễn Hữu Khôi 07 Feb '24

07 Feb '24

Hello guys. Could you share with me some experience about using Magnum CAPI in production? https://github.com/vexxhost/magnum-cluster-api Thank you so much. Nguyen Huu Khoi

6 44

Cinder Bug Report 2024-02-07
by Jon Bernard 07 Feb '24

07 Feb '24

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> Undecided - Service cinder-backup failed when Swift with TLS enabled <https://bugs.launchpad.net/cinder/+bug/2051985> - Status: In Progress - hpe xp: wrong copyrights in test scripts <https://bugs.launchpad.net/cinder/+bug/2052409> - Status: In Progress - GRUB menu format error <https://bugs.launchpad.net/cinder/+bug/2052414> - Status: New Thanks, -- Jon

1 0

[cinder][vendors] Third party CI compliance check
by Rajat Dhasmana 07 Feb '24

07 Feb '24

Hello Vendors, This is related to the original discussion on the ML thread[1]. We have noticed that a lot of the drivers don't have their CI reported on a patch in 2024. Based on the last CI report that I checked[2], the number comes out to be 32 though it's not an accurate measure of the inactivity in the project. The following cases are possible: 1. The driver that doesn't have active CI reporting is already marked unsupported 2. The driver is supported but CI is not actively maintained 3. The CI information is not accurate in the wiki page If it's case 2, vendors should look into their CI and fix it else the driver will be marked unsupported in the current or upcoming release. If it's case 3, make sure to have updated CI info in the wiki page. Let's take an example of the HPE driver. The last seen status is shown as: last seen: 2016-08-09 but the driver is actively reporting on patches. The issue here is either: 1. The CI name in the volume driver is not pointing to the correct wiki page[3] 2. The wiki page does not have correct information about CI[4] Vendors should look into updating their CI related information before the midcycle-2, which is going to be held on 14th Feb, 2024 from 1400-1600 UTC[5]. Since we only have the cireport[2] as the source of truth, we will be looking at the vendor drivers that don't have a recent last seen date and start marking them unsupported during the midcycle-2. Any query is welcome on this thread or during the midcycle-2 topic discussion. [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [2] http://cinderstats.ivehearditbothways.com/cireport.txt [3] https://opendev.org/openstack/cinder/src/branch/master/cinder/volume/driver… [4] https://wiki.openstack.org/wiki/ThirdPartySystems/HPE_Storage_CI [5] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… Thanks Rajat Dhasmana

3 2

[all] SLURP support survey
by Mark Goddard 07 Feb '24

07 Feb '24

Hi, The Kolla project is planning to support SLURP upgrades [1] in the Caracal release cycle, allowing users to upgrade from Antelope to Caracal. There are two areas in which I'd like to request information from the various project teams. # 1. SLURP support We understand that for various reasons there can be a gap between TC resolutions and implementation across projects. Using some rudimentary grepping through various codebases I found that many projects have added the grenade-skip-level job (or a variation of it) to their CI pipelines, and a few mention SLURP in their release notes. There's little mention of it in documentation at this stage. AFAICT the following projects have SLURP upgrade jobs: Cinder, Glance, Ironic, Manila, Neutron, Nova, Octavia While I could not find a SLURP job in these: Barbican, Bifrost, Blazar, Cloudkitty, Designate, Heat, Horizon, Keystone, Magnum, Placement Question: Does your project explicitly support SLURP upgrades? Do you have or are you planning to add testing and documentation for SLURP upgrades? # 2. Rolling SLURP upgrades The TC resolution [1] states that rolling upgrades are optional for SLURP releases. This could affect the upgrade procedure required in Kolla Ansible. Nova mentions in its Antelope release notes that it supports rolling SLURP upgrades, but I could not find any information from other projects. It would be helpful if this was documented for each project. Question: Does your project support or plan to support rolling upgrades? If changes to the upgrade procedure for SLURP are required, are they documented? Thank you in advance for your responses. Apologies if I have missed any obvious source of information on this. Regards, Mark [1] https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad…

7 7

[largescale-sig] Next meeting: February 7, 9utc
by Thierry Carrez 07 Feb '24

07 Feb '24

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 9UTC, our EU+Asia time. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240207T09 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

2 2

[Kolla][Octavia] worker unable to connect amphora instance
by Jayesh Chaudhari 06 Feb '24

06 Feb '24

Folks, I have set up kolla-ansible yoga openstack and configured Octavia using VLAN. But when I am trying to create a LB, it is stuck in pending create then eventually failed. And in logs I can see octavia-worker unable to connect to amphora instance. Is there any sanity which I can do to check if my implementation is correct ? Or am I missing something? Please advise. My configuration in global.yml enable_octavia: yes octavia_network_interface: "vlan.2140" octavia_auto_configure: yes octavia_amp_flavor: name: "amphora" is_public: yes vcpus: 2 ram: 1024 disk: 5 octavia_amp_security_groups: mgmt-sec-group: name: "lb-mgmt-sec-grp" rules: - protocol: icmp - protocol: tcp src_port: 22 dst_port: 22 octavia_amp_network: name: lb-mgmt-net provider_network_type: vlan provider_segmentation_id: 2140 provider_physical_network: physnet1 external: false shared: false subnet: name: lb-mgmt-subnet cidr: "10.145.50.128/26" allocation_pool_start: "10.145.50.135" allocation_pool_end: "10.145.50.190" gateway_ip: "10.145.50.129" enable_dhcp: yes octavia_amp_image_tag" "amphora" octavia_loadbalancer_topology: "SINGLE" Thanks, Jayesh

3 8

[tc] Next Technical Committee Meeting Tomorrow, Feb 3, 1800 UTC
by Jay Faulkner 06 Feb '24

06 Feb '24

Hi all, The next scheduled meeting of the Technical Committee is tomorrow. This meeting will be held primarily in Zoom, with minutes kept in IRC. Interested parties can join at https://us06web dot zoom dot us/j/87108541765?pwd=emlXVXg4QUxrUTlLNDZ2TTllWUM3Zz09 (repair the URL first). The proposed agenda ia: Agenda - Roll call - Follow up on tracked action items - Gate health check - Implementation of Unmaintained branch statuses - 2024.1 TC Tracker - https://etherpad.opendev.org/p/tc-2024.1-tracker - Open Discussion and Reviews

1 1

[openstack-helm] Remove Calico chart
by Vladimir Kozhukalov 06 Feb '24

06 Feb '24

Hi everyone, I would like to suggest removing the calico chart from the openstack-helm-infra repository which does not seem worth it to support any more. Tigera provides great tools for managing Calico deployments (helm chart, operator and even plain kubectl manifest). Also there are plenty of other networking solutions on the market and it looks like users can choose on their own the CNI implementation. There have not been many contributions to this chart for quite some time and we don't use this chart in any test jobs. In the deploy-env role we use the upstream Calico manifest [1]. Having said that, I think that we can remove it immediately even without any depreciation period. Opinions are welcome. [1] https://opendev.org/openstack/openstack-helm-infra/src/branch/master/roles/… -- Best regards, Kozhukalov Vladimir

4 3

Glance image import to AWS S3 fails for files larger than 5GB
by Shrishail K 05 Feb '24

05 Feb '24

Hi Team, I have a use case where I need to replicate images from file store to S3 store. While image creation directly on S3 works fine with large files over 5G. The same fails when attempted via image-import with copy-image method. The failure is due to AWS rejecting a single object upload operation where the object size is over 5GB. What I see from logs is that direct image creation on S3 uses multipart upload when images are large. However, I fail to see the same happening when image import was used to copy an image from file to s3. Is this a known issue? Or Am I missing some configs related to image-import? Openstack version: Antelope Client version: 6.4.0 Thanks, Shrishail

3 14

[puppet] EOL plan of wallaby, xena and yoga
by Takashi Kajinami 05 Feb '24

05 Feb '24

Hello, I'm sending this as an early announcement of my current plan about these old stable branches in Puppet OpenStack project. Because we've not see any interest to backport changes to these stable branches and we have limited capacity to maintain our project, I'd propose transitioning EOL these old stable branches by the following steps. * stable/yoga is transitioned to unmaintained/yoga but we may not work on maintaining it now (which eventually means it's abandoned right after its transition to unmaintained status). We'll move it to EOL at the next cadence, when zed is transitioned to unmaintained). * wallaby and xena will become immediate candidates for EOL so we'll just move the EOL process forward. If you have any concern, then please let me know. We'll formally work on these processes in the release patches. [1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmainta… -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 0